Text |
Invalid data for batch environment. |
Explanation |
In a batch environment, the input for an UNCATALOG/PURGE/SCRATCH command can only consist of a list of names for Natural modules/programs. At least 1 name must be entered. A maximum of 40 names can be entered. Asterisk notation is not permitted. |
Action |
Enter one or more valid names. |
Text |
Only one generic key permitted. |
Explanation |
Only one generic key is permitted per invocation of the UNCAT/PURGE/ SCRATCH command. A generic key is a character string, which may be empty, truncated by an asterisk. The use of a generic key results in the display of a menu which contains all modules/programs starting with the character string. These modules/programs may be marked for further processing. |
Action |
Enter valid data. |
Text |
Do not use both, list of names and asterisk notation. |
Explanation |
For the UNCATALOG/PURGE/SCRATCH commands, you can either enter a list of Natural module/program names or use asterisk notation, but not both. |
Action |
Correct error. |
Text |
No module(s)/program(s) found in current library. |
Explanation |
No module/program was found which meets the search criteria. |
Action |
Make sure that the correct search criteria were used. |
Text |
New error range may not overlap the current error range. |
Explanation |
When renumbering (renaming) ranges of errors, overlaps of ranges are not permitted within the same application (for reasons of data integrity). The NEW ERROR FROM must be smaller than the original ERROR FROM or greater than the original ERROR TO. Example: When renumbering errors 10 to 20 as 13 to 23; number 10 would be moved to 13, but 13 would be moved to 17, and 17 would be moved to 20, etc.; thus, error number 10 would be duplicated. If the NEW ERROR FROM were smaller than 10 or greater than 20, this . would not occur. If you cannot avoid overlapping with the ranges of numbers available to you, renumber the errors to a dummy application and then from the dummy application to the original application. |
Action |
Check the error numbers and the application, and correct the error. |
Text |
User exit was invoked but no longer exists. |
Explanation |
At initialization of SYSMAIN, the user exit 1 and/or 2 was active, but during processing the user exit could not be invoked. This may occur if the cataloged object is not cataloged in the SYSMAIN library. |
Action |
No action required. SYSMAIN will no longer invoke the user exit which caused the error. |
Text |
Predict file invalid for processing of XREF data. |
Explanation |
When XREF data are processed (XREF parameter set to 'Y', 'F' or 'S'), the Predict (FDIC) file must be a valid file for Predict Version 2.3 or above. (With SYSMAIN, you may use the command 'SET FDIC' to override the current Predict file setting.) This error also appears if you are processing sets and the FDIC file is not a valid Predict file. |
Action |
Use a valid Predict file, or set the XREF indicator to 'N', or set the set number to '0'. |
Text |
Conflicting or too many types. |
Explanation |
The command DELETE has a TYPE option. The number of types entered in the delete request was too large. This is either because types 'X' or 'U' where expanded and the resulting list became too large, or because repeated or redundant entries were found. |
Action |
Repeat the request, either with fewer types or, if the default '*' is suitable, without the TYPE specification. |
Text |
Do not enter both, asterisk notation and list of names. |
Explanation |
For the UNCATALOG/PURGE/SCRATCH commands, you can either enter a list of Natural module/program names or use asterisk notation, but not both. |
Action |
Correct error. |
Text |
Object is protected by Predict Application Control. |
Explanation |
You cannot maintain the selected object because it is under the control of Predict Application Control. |
Action |
Contact your Predict Application Control administrator. |
Text |
Set ... cannot be found. |
Explanation |
The specified set cannot be found. |
Action |
Make sure that you have specified the correct User, Library, Library DBID/FNR, FDIC DBID/FNR, and Set Number. |
Text |
PC Download must be 'Y' or 'N'. |
Explanation |
When you export/download Natural objects to a PC, this option must be set to either 'Y' (export) or 'N' (normal processing). |
Action |
Specify correct value. |
Text |
Work files 6 + 7 must be assigned to PCNEW for download. |
Explanation |
When you use the PC Download option, work files 6 and 7 must be assigned to PCNEW. |
Action |
Assign work files 6 and 7. |
Text |
Library range must not be specified for sets. |
Explanation |
When a set is used as source location of objects, you can only specify specific library names, but not a range of libraries. |
Action |
Provide correct library specification. |
Text |
Unload type must be 'A', 'C', 'S' or 'W'. |
Explanation |
The unload type must be one of the following: A - all objects (cataloged or saved), C - cataloged objects, S - saved objects, W - stowed objects. |
Action |
Specify a correct value. |
Text |
Conflicting request. |
Explanation |
The command DELETE has a TYPE option. If views (DDMs) are to be deleted, you must not specify objects of other types in that (sub-)command. |
Action |
Delete DDMs (views) separately. |
Text |
When object is specified, library name is also required. |
Explanation |
When you specify an object name for unloading/loading, you must also specify a library name to identify the library in which the specified object is stored. |
Action |
Specify library name. |
Text |
Error in DELETE command (invalid syntax). |
Explanation |
The DELETE command specified could not be executed, because it does not comply with the rules for command syntax. See 'System Commands' in the documentation for the correct syntax. |
Action |
Enter a valid command (with fewer options). |
Text |
Compare option must be 'S' (short) or 'D' (differ). |
Explanation |
See the Natural SYSMAIN utility documentation for details. |
Action |
Specify correct value. |
Text |
Invalid command with a versioned library. |
Explanation |
Once a Natural library or application has been defined as being 'versioned', the commands STOW, CATALOG, UNCATALOG, PURGE and SCRATCH must not be used on any programming objects. |
Action |
Use the STOWALL or VERSION utility to circumvent the problem. |
Text |
Compare only available with Predict Application Control. |
Explanation |
SYSMAIN's Compare option can only be used if Predict Application Control (PAC) is installed. If PAC is installed but Compare still does not work, use the SYSMAIN command 'SET FSEC' to specify the FSEC source location where PAC is installed. |
Action |
Do not use Compare if PAC is not available; or specify valid FSEC source location before you use Compare. |