Text |
Object replaced. |
Explanation |
During the load process an object description in Predict has been replaced. |
Text |
File type for file changed to 'S'. |
Explanation |
If you load a VSAM file, which was stored in Predict Version 1, the file type is set to 'S' in Predict Version 2, because some attributes of the VSAM file definition are missing. |
Action |
Change manually the SEQUENTIAL FILE in a VSAM FILE and add the required attributes. |
Text |
Adabas field name missing. |
Explanation |
During the load process a field without an Adabas short name was laoded. This message is a warning. Some files require to all fields an Adabas short name. The field was loaded, but the file contains now incorrect data. Please define to those fields the Adabas short names. |
Action |
Correct the invalid field. |
Text |
FDT incorporated. |
Explanation |
The FDT has been incorporated successfully. |
Text |
Master field missing. |
Explanation |
If you load a userview and no related Adabas field in Predict Exists, this message will be sent. |
Action |
Load first the related Adabas file. |
Text |
Natural Security not installed. |
Explanation |
The Natural Security feature is not installed. No Security options are available. |
Action |
Either do not specify Security options or install the Natural Security System. |
Text |
First character of PREFIX not alpha. |
Explanation |
The PREFIX must start with an alpha character. |
Action |
Check prefix and correct error. |
Text |
Only command VERSIONS allowed. |
Explanation |
Message occurres, if you want to unload predict version 1 data with command 'UNLOAD'. |
Action |
Enter command VERSIONS. |
Text |
No related master file found. File not loaded. |
Explanation |
If you want to load a User view and no related Adabas file exists, this message will be sent. |
Action |
Please load first the Adabas file. |
Text |
User exit program missing. |
Explanation |
IF a USER EXIT should be activated via the Predict DDA SERVICES the USER EXIT program must exist. |
Action |
Catalog the user exit program. |
Text |
Enter 'O', 'N', 'Y', or 'F'. |
Explanation |
The possible values of general system default parameters EDIT OWNER/DESCRPTION are O, N, Y or F. See documentation for further information. |
Text |
File is not locked. |
Explanation |
If you use the RECOVER function for a file which is not locked, This message will be sent. |
Action |
Check FILE-ID. |
Text |
USER VIEW not loaded, because related MASTER FILE was rejected. |
Explanation |
A USER VIEW should be laoded, but the related MASTER FILE was rejected, because its file number was not unique. |
Action |
Check the used file numbers. |
Text |
If pre-processor specified, no Natural data allowed. |
Explanation |
Natural parameter data may not be used when deleting active cross references using the Predict pre-processor. |
Action |
Do not specify Natural data. |
Text |
If PROGRAM-ID is specified, LIBRARY-ID must be specified too. |
Explanation |
If you want an evaluation by PROGRAM name, you must also specify the LIBRARY NAME. Its allowed to specify only a LIBRARY name. |
Action |
Specify library name. |
Text |
Abend data of preprocessor deleted. |
Explanation |
Active references will also be stored in the data dictionary if the preprocessor terminates with condition code greater zero. These abend data can be deleted by a special function of DDA SERVICES. |
Text |
More than 130 fields are undefined. |
Explanation |
Maximal 130 fields, which are used but not defined in Predict, are displayed. |
Action |
Define the used fields in Predict. |
Text |
Xref data deleted. |
Explanation |
This message tells you that active crossreference records have been deleted successfully. |
Text |
Please enter User ID or '.'. |
Explanation |
When using the owner editor, you may enter the owners of an object. If an owner has no users defined, it will be marked with a '?'. To define one or more users for such an owner, enter .E in the respective editor line; then enter a User ID for the new user description. |
Action |
Enter a new User ID or a '.'. |
Text |
SUPER Natural only possible, if file has security definitions. |
Explanation |
IF Natural Security is active, the generation of a SUPER Natural file entry is only possible if also Security definitions for the file are available. |
Action |
Generate also Security definition. Enter 'Y' for Natural Security. |
Text |
Copy-field ID or Copy-file ID missing. |
Explanation |
An attempt was made to copy a field without having specified a Copy-field ID. A field can be copied from one file to another or into the same file by changing its name. |
Action |
Enter either a Field ID or a File ID. |
Text |
Start-field ID not found. |
Explanation |
The Start-field ID was not found in the file. A valid Start-field ID must be entered in order to copy fields. |
Action |
Enter a valid Start-field ID. |
Text |
Start-field ID missing. |
Explanation |
No Start-field ID was entered. |
Action |
Enter a Start-field ID. |
Text |
Do not specify both Field ID and File ID for start field. |
Explanation |
The selection can be performed in two ways: either all fields from one file are displayed for selection, or all files containing the field entered are displayed. |
Action |
Enter either a Field ID or a File ID; do not enter both. |
Text |
No SUPER Natural possible if status private. |
Explanation |
If Natural Security is active and a file is declared as private no generation of a SUPER Natural file entry is possible. |
Action |
Change status of the file, if necessary. |
Text |
SUPER Natural file added. |
Explanation |
At generation DDM for the file a SUPER Natural entry has been generated. |
Text |
Hit enter to return to menu. |
Explanation |
This message is issued when an error is encountered during the generation of a Data Definition Module; a specific error message is also returned with this message. |
Action |
Hit enter and the menu will be displayed. Hit enter to go back to menu; correct error. |
Text |
Invalid offset or length of primary key. |
Explanation |
This error message occurres at generation DDM of logical VSAM file. Offset and length of the primary key in the logical VSAM file must be equate to the offset and length of the primary key in the physical VSAM file in consideration with the length of the Prefix. If the VSAM prefix was not specified at maintenance logical VSAM file, the standard VSAM prefix 'file number' will be taken. |
Action |
Correct offset or length of the primary key in the logical or physical VSAM file. |
Text |
Incorrect length for primary key. |
Explanation |
Correct length of the primary key. |
Text |
Field moved successfully. |
Explanation |
The field was moved successfully within the file. |
Text |
Object purge was not confirmed. |
Explanation |
When an object should be deleted in Predict, the system needs an additional confirmation. In the present case, the user abends the PURGE function and the object still remains in the dictionary. |
Text |
Object purged successfully. |
Explanation |
The object description was deleted from the dictionary. All other entries belonging to the object remain in the dictionary. |
Text |
Object scratched successfully. |
Explanation |
The object and all objects belonging to that object have been deleted from the dictionary. |
Text |
Enter 'DELETE' or 'SCRATCH' or '.'. |
Explanation |
The user has been prompted for an confirmation: if 'DELETE' is entered, only the specified object will be deleted; if 'SCRATCH' is entered, the object and all its dependent objects will be deleted; if input is '.', no object will be deleted. |
Action |
Enter the desired option. |
Text |
Alternate index not on that offset. |
Explanation |
The defined offset of the alternate index is wrong. |
Action |
Check offset. |
Text |
Invalid length of alternate index. |
Explanation |
The defined length of the alternate index is wrong. |
Action |
Check length of the alternate index. |
Text |
No generation for conceptual or standard file allowed. |
Explanation |
The generation of copy code is not allowed for conceptual and standard files. You must copy the file definition to another file, which is not of type standard or conceptual, then you can start the generation. |
Action |
Check file type or use another file. |
Text |
No file number available, file not loaded. |
Explanation |
All file numbers with the same last 3 digits of the specified file number are used. For example the file numbers 0001, 1001, 2001, 3001,........................, 9001 all used. |
Action |
Use another file number. |
Text |
Invalid Adabas file number, not loaded. |
Explanation |
The last 3 digits of the file number greater 255. |
Action |
Check file-number and correct error. |
Text |
Enter 'DELETE' or '.'. |
Explanation |
The user has been prompted for an confirmation: if 'delete' is entered, the specified object will be deleted; if '.' is entered, no object will be deleted. |
Action |
Enter the desired option. |
Text |
All keywords have relations. |
Explanation |
Every keyword defined in Predict has relations. |
Text |
No object was selected. |
Explanation |
A menu for selecting an object from a list was displayed, and the user was prompted to select one of the objects. None was marked. |
Text |
An object was selected. |
Explanation |
The user was prompted to select an object from a list. An object was marked by the user. This message indicates that Predict has carried out the selection. |
Text |
The RENAME function was not performed. |
Explanation |
After the RENAME function has been invoked, the user did not enter the new name for the object. Therefore, the RENAME function did not take place. |
Text |
For copy a user view file number cannot change. |
Explanation |
If you copy a user view from an Adabas master file, the file number cannot be changed. |
Action |
Enter the file number of the master file. |
Text |
Indicator not '+' OR '-'. |
Explanation |
The indicator tells the editor whether the entered line command
should be performed after the line ('+') or before the line ('-')
where the command was entered. For example, the line command
'.W' will open a window after the line where this command
has been entered if the value of the indicator is '+' and will
open the window before the mentioned line if the value of the
indicator is '-'. |
Action |
Enter '+' or '-' for the indicator. |
Text |
Target file does not exist. |
Explanation |
An attempt was made to copy a field to a non-existant file. |
Action |
Enter a valid File ID. |
Text |
File tested successfully. |
Explanation |
The file was tested against the FDT: no differences between the FDT and the file were found. |
Text |
File tested with error. |
Explanation |
During a test of a file against the FDT, differences were found (for example, a field name in the file was not found in the FDT). |
Action |
Check file and correct error. |
Text |
The file entered is not accessible. |
Explanation |
Adabas was unable to gain access to a file. Probable reasons are: - file not in data base; or - authorization level too low to gain access; or - file is locked. |
Action |
Correct error and retry. |