Text |
Invalid range specification. |
Explanation |
The range for a search criterion was specified incorrectly. The start value must be less than or equal to the end value. |
Action |
Correct error. |
Text |
No program/module with specified criteria found. |
Explanation |
No program/module in the user"s library meets the specified search criteria. |
Action |
Check data and specify search criteria more precisely. |
Text |
Function disallowed by security definition. |
Explanation |
The desired function is disallowed by the Natural Security application profile. |
Action |
Contact your Natural Security administrator. |
Text |
No module found in library. |
Explanation |
While executing the SIZE command, no module which meets the search criteria was found. |
Action |
Check module name. |
Text |
"Size" operation protected by security definition. |
Explanation |
To execute the SIZE command in a Natural Security environment, you must be allowed to use the command EXECUTE. |
Action |
Contact your Natural Security administrator. |
Text |
No objects found for specified "scan" criteria. |
Explanation |
SCAN will do processing only according to the criteria specified. Only the objects which satisfy the specifications will be displayed, otherwise SCAN will return to the menu. |
Action |
No action required, since SCAN has terminated normally. |
Text |
Invalid field combination with "rename" function. |
Explanation |
When you use the "rename" function of SYSMAIN and have entered a specific name in the Object Name field, you must also enter a New Name. Alternatively, the range notation using a "?", "<", ">" or "*" may be used; in which case no New Name is to be specified. |
Action |
Check values specified and correct error. |
Text |
File type is not valid for specified file. |
Explanation |
With SYSMAIN, only specific file types are supported. The file type is determined by the DBID and FILE number specified for the source and target files. For valid file types, see the relevant Natural documentation. |
Action |
Check the DBID and FILE number specified and correct them. |
Text |
Access to library is not allowed. |
Explanation |
When you use the SYSMAIN utility under Natural Security, you are not allowed to access a "private library" of another user. Only access to your own (private) library is possible. This error occurs: - if you perform the LIST/FIND function and attempt to select a private library; or, - if you perform the COPY/MOVE/DELETE/RENAME function and have specified a private library as source/target library. |
Action |
Use only libraries which you are allowed to use. |
Text |
New "rename" data must be different. |
Explanation |
When using the RENAME function of SYSMAIN, the new data of the object (saved or cataloged), profile or view must be different from the old data. |
Action |
Correct error. |
Text |
Enter either a valid function code or a command. |
Explanation |
Either a valid function code or a command must be entered in the appropriate fields. |
Action |
Enter either a valid function code or a valid command. |
Text |
Enter a valid library name. |
Explanation |
A library name must be specified. |
Action |
Check the library name specified and correct the error. |
Text |
Invalid character in library name. |
Explanation |
A valid library name must be specified. An asterisk (*) or a question mark (?) indicating a range of values is not permitted. |
Action |
Enter a valid library name. |
Text |
Database identification must be 0 - 253. |
Explanation |
A valid database identification (DBID) must be specified. Valid DBIDs are: 0 - default database 1 - 253 - specific database. |
Action |
Enter a valid database identification. |
Text |
File number must be 1 - 255. |
Explanation |
A valid system file number in the range from 1 to 255 must be specified. |
Action |
Enter a valid file number. |
Text |
Invalid type of Natural system file. |
Explanation |
An invalid value for system-file identification was entered. Possible values are: A - Adabas system file, V - VSAM system file. |
Action |
Enter "A" or "V" as type of system file. |
Text |
Invalid name specified for file. |
Explanation |
If the Natural system file is not an Adabas file, the name of the system file being accessed must be specified. This applies to the following system file types: V - VSAM 2 - DB2 U - USER D - DL/I S - SESAM |
Action |
Enter a value for the "Name" field. |
Text |
Nothing found for this request. |
Explanation |
Either no data meet the specified selection criteria, or you did not request any processing to be done from the selection screen. This is a normal termination message. |
Action |
No action required. |
Text |
Function completed successfully. |
Explanation |
The function has successfully terminated, and all data selected have been processed normally. |
Action |
No action required. |
Text |
Not all module(s)/program(s) were processed. |
Explanation |
The function was not executed for all specified module(s)/program(s). Either the module specified in the selection menu was deleted in the meantime by another user, or the module(s)/program(s) could not be overwritten because the REPLACE option was set to "NO". |
Action |
Correct error. |
Text |
Syntax error in command line. |
Explanation |
A syntax error was detected when evaluating the command line during command processing: the command to be processed was not a valid command Either you have entered a command which does not exist, or you have specified a command incorrectly (e.g. wrong sequence of parameters). The actual command being processed may be indicated in parentheses at the end of the error message. |
Action |
Check the command line and correct the error. |
Text |
Invalid object name specified. |
Explanation |
A valid name must be entered in the field "Object Name" before processing can continue. |
Action |
Check data and correct error. |
Text |
No XREF information found for object. |
Explanation |
The XREF indicator is set to either "Y" or "F", but the specified Predict (FDIC) file contains no XREF information for the object being processed. |
Action |
Check the FDIC file specified, the XREF indicator, and the status of the XREF information for the object in error. |
Text |
Libraries listed successfully. |
Explanation |
The libraries satisfying the specified search criteria were listed successfully. |
Action |
No action required. |
Text |
Selected number out of range. |
Explanation |
Only numbers displayed on the selection menu may be selected. |
Action |
Enter a valid number. |
Text |
Program does not exist. |
Explanation |
No program exists for the selected number. |
Action |
Select another number. |
Text |
No libraries found. |
Explanation |
No library was found which meets the search criteria. |
Action |
Verify search criteria. |
Text |
Program listed successfully. |
Explanation |
The Natural program was listed successfully. |
Action |
No action required. |
Text |
Function not allowed by security definition. |
Explanation |
To execute the desired function in a Natural Security environment, the library to be processed must be either your "private library", a public library, or a people-protected library of which you are an "owner" (if co-owners exist, the required countersignatures must be obtained). Moreover, the use of the corresponding Natural commands - SAVE, CATALOG, STOW, SCRATCH, PURGE, UNCATALOG - must be allowed in that library. |
Action |
Do not use this function; or contact your Natural Security administrator. |
Text |
Range not permitted in batch processing. |
Explanation |
When using the RENAME function of the utility SYSMAIN via a direct command in batch mode, a range of modules/programs must not be specified with the "*" or "?" notation. |
Action |
Do not use "*" or "?" notation in batch mode. |
Text |
Enter valid command, or enter "?" for help. |
Explanation |
An invalid command was entered. For a list of valid command, you may enter a "?". |
Action |
Enter a valid command, or enter a "?" for help. |
Text |
Buffer pool maintenance failed. |
Explanation |
The Natural buffer pool maintenance failed, because the Natural buffer pool is either not installed or has been disabled after an ABEND. |
Action |
Contact your Natural administrator. |
Text |
Buffer pool maintenance performed. |
Explanation |
Maintenance of the Natural buffer pool was performed. |
Action |
No action required. |
Text |
TP user ID required. |
Action |
Enter a valid TP user ID. |
Text |
Invalid database ID. |
Explanation |
A database identification in the range 0 - 255 must be entered. |
Action |
Enter a valid database identification. |
Text |
Invalid file number. |
Explanation |
A file number in the range from 0 to 255 must be entered. |
Action |
Enter a valid file number. |
Text |
Please enter a valid library name. |
Explanation |
A valid name for a Natural library must be entered. |
Action |
Enter a valid library name. |
Text |
Please enter a valid module name. |
Explanation |
A valid name for a Natural module must be entered. |
Action |
Enter a valid module name. |
Text |
Currently no logical files available. |
Explanation |
The utility makes use of "logical files" to perform any required processing. If all logical files are in use, processing is terminated abnormally. SYSPROF may be used to display the current file settings. |
Action |
Contact your database administrator for additional help. |
Text |
Library is not defined to Natural Security. |
Explanation |
You have requested access to a library which is not defined to Natural Security. In the case of SYSMAIN, this may occur when you are maintaining libraries which are defined to another security environment. If you wish to do maintenance across security environments, you should use the SYSMAIN command "CMD FSEC". For further information, see the Natural documentation. |
Action |
Check the selection criteria and correct the error. |
Text |
Invalid owner/co-owner confirmation. |
Explanation |
The countersignature specified for an owner-protected application must be valid for a co-owner to use an application; or the user is NOT an owner of the application. |
Action |
Specify the correct countersignature for the security environment being accessed. |
Text |
Invalid DBID and/or FNR specified for a library. |
Explanation |
The DBID and FNR specified for a library protected by Natural Security must correspond to the DBID and FNR specified in the security profile for the library. |
Action |
Either correct the DBID/FNR, or change the FSEC definition using the "CMD FSEC" command. |
Text |
Invalid Predict file(s) defined. |
Explanation |
The FDIC parameter is pointing to a database and/or file which is not a valid file for Predict. This causes an error during the deletion of XREF data. - If the FDIC parameter is correct, you should verify the settings of the SYSMAIN FDIC database(s) and/or file(s), since these will override the session FDIC parameter. Note that with XREF support the Predict version must be 2.3 or above. - If the XREF parameter is set to "N", no check will be done online. In batch, the nucleus should not have the XREF module linked. |
Action |
Check the current settings of the Natural parameter FDIC and the SYSMAIN FDIC parameters, and correct the error. |
Text |
Normal completion, but some data were rejected. |
Explanation |
During processing of a function which does not result in the display of a selection screen, processing continues even if objects are rejected. There are numerous reasons why objects are rejected, and these are listed under error NAT4810. If you wish to monitor the status of each each object as it is processed, use the selection screen (using the "?" option). This is a normal end-of-processing message. |
Action |
No action required. |
Text |
Invalid error number specified. |
Explanation |
The FROM error number has been specified incorrectly: either
no range notation has been specified, the FROM number is greater
than the TO number, or the range notation is invalid.
In batch, this error may also occur if any of the specified error
numbers (ERROR FM, ERROR TO, NEW ERROR FM, NEW ERROR TO) are not
numeric. Valid specifications of numeric numbers are:
1 or 01 or 001 or 0001
|
Action |
Check the error number specifications, and correct the error. |
Text |
Invalid language code specified. |
Explanation |
The language code specified is invalid. See the Natural documentation for further information on language codes. |
Action |
Enter a valid language code. |
Text |
Invalid processing request for extended error message. |
Explanation |
When moving, copying or renaming an extended error message, there must always be a corresponding short error message. If there is no short error message in the source environment, the extended error message will not be processed. If there is not short message in the target environment, this error message will be output. Processing of both, short and extended messages, together is valid. |
Action |
Correct error. |
Text |
Invalid error application specified. |
Explanation |
The specified error application is invalid for the requested function. It may be a non-existent application, or you have tried to move, copy or rename a user error message to a system error message. Deletion of a system error message has been disallowed. The message may, however, be moved, copied, or renamed. |
Action |
Check the application indicated, and correct the error. |
Text |
Invalid error number specified with "rename". |
Explanation |
When renaming (renumbering) error messages, all error number
specifications (ERROR FM, ERROR TO, NEW ERROR FM, NEW ERROR TO) must
be numeric and follow the rules listed below:
1) The numbers must be in the correct combination as follows:
A) only ERROR FM.
B) ERROR FM and ERROR TO.
C) ERROR FM and NEW ERROR FM.
D) ERROR FM, ERROR TO, NEW ERROR FM and NEW ERROR TO.
2) If the range notation is used, the NEW ERROR FM must be by at
least 2 higher than the ERROR FM.
3) If the range notation is used, the difference between ERROR FM
and ERROR TO must be the same as NEW ERROR FM and NEW ERROR TO.
|
Action |
Correct the error. |
Text |
This feature is not implemented for VSAM system file. |
Explanation |
To use this feature, a Natural system file is required that is contained within an Adabas database. |
Action |
Select another feature. |