| Text | Object added successfully. |
| Expl. |
The object was added successfully. |
| Text | Object copied successfully. |
| Expl. |
The copy function was successfully executed. |
| Text | Object modified successfully. |
| Expl. |
The modify function was successfully executed. |
| Text | Owner not defined. |
| Expl. |
The owner record must be successfully added to the dictionary before the owner may be declared as an owner for other dictionary objects. |
| Actn. |
Enter a valid owner id or leave blank. |
| Text | Keyword is not defined. |
| Expl. |
A keyword must exist within the dictionary before it can be assigned to any other dictionary objects. |
| Actn. |
Enter a valid keyword or leave blank. |
| Text | Unable to edit object if editor is active. |
| Expl. |
Extended descriptions, verifications or owner lists cannot be modified while a list of subsequent objects is being modified. |
| Actn. |
Enter "N" for edit-description, edit-verification or edit-owners. |
| Text | Database is not of type ... |
| Expl. |
At generation DDM the file type will be checked against the type of the database. Since Natural V2.1 the VSAM database number is no longer restricted to 254. The database type to file type "A" and "U" must be "A" and to file type "V", "L", "W" and "R" must be "V". |
| Actn. |
Enter correct database id. |
| Text | Object in use. |
| Expl. |
Conflict during editing function due to multiple updates to the same object by another user. |
| Actn. |
Restart the edit session. |
| Text | No more than XXX objects supported. |
| Expl. |
An attempt was made to add more than XXX objects to an other object. You may define up to 500 subsequent objects to an object, 99 owners to any object and 30 different codes for a file. Further additions will be rejected. |
| Actn. |
Establish whether all objects (e.g., files) are necessary. Delete all unnecessary objects. |
| Text | Correct the error or hit "enter" to edit object list. |
| Expl. |
If an error was detected during the catalog or check function, the error may be corrected immediately or the user may return to the full screen editor by hitting enter. |
| Actn. |
Hit enter or correct the error. |
| Text | Object structure cataloged. |
| Expl. |
The catalog function terminated successfully. |
| Text | Duplicate object found. |
| Expl. |
In editing the elements of an object, duplicated element names have been found during the catalog or check process. |
| Actn. |
Correct the duplicate name or hit enter to return to the full screen editor. |
| Text | First character of name not alpha. |
| Expl. |
All object names must start with an alpha character and must be at least 3 characters long. |
| Actn. |
Correct the object name. |
| Text | Object displayed successfully. |
| Expl. |
The display function has been successfully completed. |
| Text | Invalid object. |
| Expl. |
An attempt was made to reference a nonexistent object type. |
| Actn. |
Enter a correct object type. |
| Text | Invalid function code. |
| Expl. |
Enter a valid Predict function. |
| Text | Function terminated. |
| Expl. |
The Predict function has been completed successfully. |
| Text | No OBJECT specified. |
| Expl. |
An Object ID must be entered. |
| Actn. |
Enter a valid Object ID. |
| Text | Object does not exist. |
| Expl. |
The specified object does not exist in the dictionary. |
| Actn. |
Enter a valid Object ID. |
| Text | More than one object found. See DBA. |
| Expl. |
More than one object was found in the dictionary. The objects in the dictionary should be unique. This is a serious error. |
| Actn. |
Stop activity immediately and contact your DBA. |
| Text | Object name already exists. |
| Expl. |
The Object ID entered already exists in the dictionary. All ID"s entered in Predict (except for the field name) must be unique. |
| Actn. |
Note also that the field names in a given file must be unique. Enter a valid Object ID. |
| Text | First character of new Object ID is not alpha. |
| Expl. |
The first character of an Object ID must be a valid alpha-character. The object name must be at least 3 characters long. |
| Actn. |
Enter a valid new Object ID. |
| Text | The function was not performed. |
| Expl. |
The function was not performed because either an invalid input was made or a field was left blank. |
| Text | File ID must be specified. |
| Expl. |
A field is uniquely defined only via the field and file name. |
| Actn. |
Enter the File ID also. |
| Text | Object explosion listed. |
| Expl. |
The explosion of an object has been displayed successfully. |
| Text | Object listed successfully. |
| Expl. |
The requested objects have been successfully listed. |
| Text | OBJECT IMPLOSION listed. |
| Expl. |
The IMPLOSION of an OBJECT has been displayed successfully. |
| Text | Object RENAMED successfully. |
| Expl. |
The RENAME of an object has been performed successfully. |
| Text | No XREF DATA found. |
| Expl. |
This message is issued by the function "DELETE XREF DATA". If the search criteria did not agree with any XREF DATA, this message is issued. |
| Actn. |
Enter valid search criteria. |
| Text | Invalid file type, file not loaded. |
| Expl. |
The file type encountered in the file record is not known to Predict. Therefore the file description has not been loaded. |
| Actn. |
Create a correct file description record. |
| Text | Maximum file number must be less than 256. |
| Expl. |
One Adabas DATABASE contains max. 255 FILES, i.e. the MAX-FILE parameter must less than 256. |
| Actn. |
Enter a number less than 256 or set the field to BLANK. |
| Text | Default conversion performed. |
| Expl. |
If the neccessary conversions from version 1 data are executed the message will be sent |
| Text | No object in hold. |
| Expl. |
The rename / renumber function issues several ETs to prevent an overflow of the Adabas hold queue. Control records are written to the Predict file every time an ET is made. If the function abends, Predict is able to backup all transactions of this function successfully. After the whole function is performed, the control records are deleted. This message is issued if no control record was found in the RECOVERY function. |
| Text | Checkpoint file number must be less than or equal to max-file-no. |
| Expl. |
The Adabas Checkpoint file number must be less than or equal to the maximum number of files specified for the data base. |
| Actn. |
Enter a valid file number or leave the field blank. |
| Text | Security file number must be less than or equal to max-file-no. |
| Expl. |
The Adabas security file number must be less than or equal to the maximum number of files specified for the data base. |
| Actn. |
Enter a valid file number or leave the field blank. |
| Text | System file number must be less than or equal to max-file-no. |
| Expl. |
The Adabas system file number entered must be less than or equal to the maximum number of files specified for the data base. |
| Actn. |
Enter a valid file number or leave the field blank. |
| Text | Natural, security and checkpoint files not different. |
| Expl. |
The Adabas checkpoint file, security file, and the Natural system file must be unique, i.e. different file numbers must be specified for each file-type. |
| Actn. |
Enter different file numbers or leave the fields BLANK. |
| Text | Natural Security file number must be less than or equal to |
| Expl. |
max-file-nr. |
| Actn. |
The Natural Security file number must be less than or equal to the maximum number of files specified for the data base. Enter a valid file number or leave the field blank. |
| Text | End of file reached. |
| Expl. |
During processing of the browse function, the end of the file has been reached. All of the fields have been processed successfully. |
| Actn. |
Note: the browse function may be terminated by hitting the correct PF key. Default is PF1. |
| Text | Predict file number must be le max-file-no. |
| Expl. |
Predict file number must be le max-file-no. |
| Actn. |
Enter a valid file number or leave blank. |
| Text | Source field name missing. |
| Expl. |
At least one field name must be entered when a phonetic, super- or sub-descriptor is defined. |
| Actn. |
Enter a valid field name. |
| Text | A superdescriptor must contain 2 - 5 fields. |
| Expl. |
2 - 5 fields must be entered when defining a superdescriptor in a file. Note that a superdescriptor containing only one field is a subdescriptor. |
| Actn. |
Enter 2 - 5 fields. |
| Text | Ending position not entered. |
| Expl. |
For every field in a sub- or super-descriptor, an ending position must be entered. No default values are assumed. |
| Actn. |
Enter a valid ending position. |
| Text | No VSAM database in Natural defined. |
| Expl. |
If no database id specified at generation DDM for VSAM file or USER VIEW, the first VSAM database number, which is defined in Natural will be assigned. In this case no VSAM database number is defined in Natural. |
| Actn. |
Contact your DBA. |
| Text | Starting position not entered. |
| Expl. |
The starting position of a field contained in a sub- or super-descriptor must be entered. No defaults are assumed. |
| Actn. |
Enter a valid starting position. |
| Text | Starting position > ending position. |
| Expl. |
The starting position entered is greater than the ending position. |
| Actn. |
Enter valid positions. |
| Text | Field is a periodic group. |
| Expl. |
A superdescriptor may not contain a field which is defined as a periodic group. However, an element of a periodic group may be contained in a superdescriptor. |
| Actn. |
Correct the field name. |
| Text | Field is a group. |
| Expl. |
A super-, sub-, or phonetic-descriptor may not contain a field which has been defined as a group. However, elements of the group may be part of a descriptor. |
| Actn. |
Enter a valid field name. |
| Text | Field is a REDEFINE. |
| Expl. |
A super-, sub-, or phonetic-decriptor cannot be defined by means of a redefined field. The field must be an Adabas field. |
| Actn. |
Enter a valid field name. |
| Text | Field is a counter field. |
| Expl. |
A super-, sub-, or phonetic-descriptor may not contain a counter field, e.g., a field which is marked as a counter field (PE-count = "C"). |
| Actn. |
Correct the field name used. |
