Natural System Error Messages 2501-2550

NAT2501: Object added successfully.

Text
Object added successfully.
Explanation
The object was added successfully.

NAT2502: Object copied successfully.

Text
Object copied successfully.
Explanation
The copy function was successfully executed.

NAT2503: Object modified successfully.

Text
Object modified successfully.
Explanation
The modify function was successfully executed.

NAT2504: Owner not defined.

Text
Owner not defined.
Explanation
The owner record must be successfully added to the dictionary
before the owner may be declared as an owner for other dictionary
objects.
Action
Enter a valid owner id or leave blank.

NAT2505: Keyword is not defined.

Text
Keyword is not defined.
Explanation
A keyword must exist within the dictionary before it
can be assigned to any other dictionary objects.
Action
Enter a valid keyword or leave blank.

NAT2506: Unable to edit object if editor is active.

Text
Unable to edit object if editor is active.
Explanation
Extended descriptions, verifications or owner lists cannot be modified
while a list of subsequent objects is being modified.
Action
Enter 'N' for edit-description, edit-verification or edit-owners.

NAT2507: Database is not of type ...

Text
Database is not of type ...
Explanation
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'.
Action
Enter correct database id.

NAT2508: Object in use.

Text
Object in use.
Explanation
Conflict during editing function due to multiple updates
to the same object by another user.
Action
Restart the edit session.

NAT2509: No more than XXX objects supported.

Text
No more than XXX objects supported.
Explanation
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.
Action
Establish whether all objects (e.g., files) are necessary.
Delete all unnecessary objects.

NAT2510: Correct the error or hit 'enter' to edit object list.

Text
Correct the error or hit 'enter' to edit object list.
Explanation
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.
Action
Hit enter or correct the error.

NAT2511: Object structure cataloged.

Text
Object structure cataloged.
Explanation
The catalog function terminated successfully.

NAT2512: Duplicate object found.

Text
Duplicate object found.
Explanation
In editing the elements of an object, duplicated element names
have been found during the catalog or check process.
Action
Correct the duplicate name or hit enter to return to the full
screen editor.

NAT2513: First character of name not alpha.

Text
First character of name not alpha.
Explanation
All object names must start with an alpha character and
must be at least 3 characters long.
Action
Correct the object name.

NAT2514: Object displayed successfully.

Text
Object displayed successfully.
Explanation
The display function has been successfully completed.

NAT2515: Invalid object.

Text
Invalid object.
Explanation
An attempt was made to reference a nonexistent object type.
Action
Enter a correct object type.

NAT2516: Invalid function code.

Text
Invalid function code.
Explanation
Enter a valid Predict function.

NAT2517: Function terminated.

Text
Function terminated.
Explanation
The Predict function has been completed successfully.

NAT2518: No OBJECT specified.

Text
No OBJECT specified.
Explanation
An Object ID must be entered.
Action
Enter a valid Object ID.

NAT2519: Object does not exist.

Text
Object does not exist.
Explanation
The specified object does not exist in the dictionary.
Action
Enter a valid Object ID.

NAT2520: More than one object found. See DBA.

Text
More than one object found. See DBA.
Explanation
More than one object was found in the dictionary. The objects in the
dictionary should be unique. This is a serious error.
Action
Stop activity immediately and contact your DBA.

NAT2521: Object name already exists.

Text
Object name already exists.
Explanation
The Object ID entered already exists in the dictionary.
All ID's entered in Predict (except for the field name) must be
unique.
Action
Note also that the field names in a given file must be unique.
Enter a valid Object ID.

NAT2522: First character of new Object ID is not alpha.

Text
First character of new Object ID is not alpha.
Explanation
The first character of an Object ID must be a valid alpha-character.
The object name must be at least 3 characters long.
Action
Enter a valid new Object ID.

NAT2523: The function was not performed.

Text
The function was not performed.
Explanation
The function was not performed because either an invalid input was
made or a field was left blank.

NAT2524: File ID must be specified.

Text
File ID must be specified.
Explanation
A field is uniquely defined only via the field and file name.
Action
Enter the File ID also.

NAT2525: Object explosion listed.

Text
Object explosion listed.
Explanation
The explosion of an object has been displayed successfully.

NAT2526: Object listed successfully.

Text
Object listed successfully.
Explanation
The requested objects have been successfully listed.

NAT2527: OBJECT IMPLOSION listed.

Text
OBJECT IMPLOSION listed.
Explanation
The IMPLOSION of an OBJECT has been displayed successfully.

NAT2528: Object RENAMED successfully.

Text
Object RENAMED successfully.
Explanation
The RENAME of an object has been performed successfully.

NAT2529: No XREF DATA found.

Text
No XREF DATA found.
Explanation
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.
Action
Enter valid search criteria.

NAT2530: Invalid file type, file not loaded.

Text
Invalid file type, file not loaded.
Explanation
The file type encountered in the file record is not known to Predict.
Therefore the file description has not been loaded.
Action
Create a correct file description record.

NAT2531: Maximum file number must be less than 256.

Text
Maximum file number must be less than 256.
Explanation
One Adabas DATABASE contains max. 255 FILES, i.e. the
MAX-FILE parameter must less than 256.
Action
Enter a number less than 256 or set the field to BLANK.

NAT2532: Default conversion performed.

Text
Default conversion performed.
Explanation
If the neccessary conversions from version 1 data are executed
the message will be sent

NAT2533: No object in hold.

Text
No object in hold.
Explanation
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.

NAT2534: Checkpoint file number must be less than or equal to max-file-no.

Text
Checkpoint file number must be less than or equal to max-file-no.
Explanation
The Adabas Checkpoint file number must be less than or equal to the
maximum number of files specified for the data base.
Action
Enter a valid file number or leave the field blank.

NAT2535: Security file number must be less than or equal to max-file-no.

Text
Security file number must be less than or equal to max-file-no.
Explanation
The Adabas security file number must be less than or equal to the
maximum number of files specified for the data base.
Action
Enter a valid file number or leave the field blank.

NAT2536: System file number must be less than or equal to max-file-no.

Text
System file number must be less than or equal to max-file-no.
Explanation
The Adabas system file number entered must be less than or equal to
the maximum number of files specified for the data base.
Action
Enter a valid file number or leave the field blank.

NAT2537: Natural, security and checkpoint files not different.

Text
Natural, security and checkpoint files not different.
Explanation
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.
Action
Enter different file numbers or leave the fields BLANK.

NAT2538: Natural Security file number must be less than or equal to

Text
Natural Security file number must be less than or equal to
Explanation
max-file-nr.
Action
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.

NAT2539: End of file reached.

Text
End of file reached.
Explanation
During processing of the browse function, the end of the file
has been reached. All of the fields have been processed successfully.
Action
Note: the browse function may be terminated by hitting the correct
PF key. Default is PF1.

NAT2540: Predict file number must be le max-file-no.

Text
Predict file number must be le max-file-no.
Explanation
Predict file number must be le max-file-no.
Action
Enter a valid file number or leave blank.

NAT2541: Source field name missing.

Text
Source field name missing.
Explanation
At least one field name must be entered when a phonetic, super- or
sub-descriptor is defined.
Action
Enter a valid field name.

NAT2542: A superdescriptor must contain 2 - 5 fields.

Text
A superdescriptor must contain 2 - 5 fields.
Explanation
2 - 5 fields must be entered when defining a superdescriptor
in a file. Note that a superdescriptor containing only one field is
a subdescriptor.
Action
Enter 2 - 5 fields.

NAT2543: Ending position not entered.

Text
Ending position not entered.
Explanation
For every field in a sub- or super-descriptor, an ending position must
be entered. No default values are assumed.
Action
Enter a valid ending position.

NAT2544: No VSAM database in Natural defined.

Text
No VSAM database in Natural defined.
Explanation
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.
Action
Contact your DBA.

NAT2545: Starting position not entered.

Text
Starting position not entered.
Explanation
The starting position of a field contained in a sub- or super-descriptor
must be entered. No defaults are assumed.
Action
Enter a valid starting position.

NAT2546: Starting position > ending position.

Text
Starting position > ending position.
Explanation
The starting position entered is greater than the ending position.
Action
Enter valid positions.

NAT2547: Field is a periodic group.

Text
Field is a periodic group.
Explanation
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.
Action
Correct the field name.

NAT2548: Field is a group.

Text
Field is a group.
Explanation
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.
Action
Enter a valid field name.

NAT2549: Field is a REDEFINE.

Text
Field is a REDEFINE.
Explanation
A super-, sub-, or phonetic-decriptor cannot be defined by means
of a redefined field. The field must be an Adabas field.
Action
Enter a valid field name.

NAT2550: Field is a counter field.

Text
Field is a counter field.
Explanation
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').
Action
Correct the field name used.