Natural System Error Messages 2801-2850

NAT2801: File must be regenerated.

Text
File must be regenerated.
Explanation
The defined Adabas file is not equivalent to the Adabas FDT. Regenerate
the Adabas file or change the file definition in Predict.
Action
Regenerate the file.

NAT2802: MODULES/REPORTS do not belong to a PROGRAM.

Text
MODULES/REPORTS do not belong to a PROGRAM.
Explanation
The subobject entered does not belong to any object. This message is
issued when, for example, a report declared in the dictionary has no
relation to any program.

NAT2803: From-date greater than to-date.

Text
From-date greater than to-date.
Explanation
The specified to-date must always be greater than from-date.
Action
Check entered dates and correct error.

NAT2804: Physical/logical file for userview does not exist.

Text
Physical/logical file for userview does not exist.
Explanation
No physical or logical file for a userview exists.
Action
Create a physical or logical file.

NAT2805: Execution of program stopped with PF-key.

Text
Execution of program stopped with PF-key.
Explanation
The execution of the program has been stopped with a PF-key.

NAT2806: Phys. VSAM file for incorporate LOGICAL VSAM file does not exist.

Text
Phys. VSAM file for incorporate LOGICAL VSAM file does not exist.
Explanation
The physical VSAM file (FILE-TYPE 'V') must be defined in the dictionary
before the related LOGICAL VSAM file (FILE-TYPE 'L') can be
incorporated.
Action
Define or INCORPORATE physical VSAM file.

NAT2807: File does not exist.

Text
File does not exist.
Explanation
An attempt was made to RECOVER a non-existent file. Please enter
the correct name of the file which is to be recovered.
Action
Enter a valid file name.

NAT2808: File cannot be recovered.

Text
File cannot be recovered.
Explanation
The file is intact. No inconsistencies were detected; therefore,
no RECOVER is permitted/necessary.
Action
Do not RECOVER intact files.

NAT2809: Subobjects having no related objects listed successfully.

Text
Subobjects having no related objects listed successfully.
Explanation
At RETRIEVAL, The sub-objects which have no relation to an object
were listed, for example: all files which have no related database
are listed.

NAT2810: All sub-objects have related objects.

Text
All sub-objects have related objects.
Explanation
At RETRIEVAL, all subobjects,which do not have any related objects
were requested. No subobjects met the required condition. For example:
all files defined in the dictionary have a relation to a report or a
module.

NAT2811: All objects have related subobjects.

Text
All objects have related subobjects.
Explanation
At RETRIEVAL, all objects that do not have any subobjects were
requested. No object met the condition. For example: all programs have
reports and/or modules.

NAT2812: The object entered has no subobjects.

Text
The object entered has no subobjects.
Explanation
In a RETRIEVAL, an object's subobjects were requested. This message
informes the user that the object has no sub-objects, for example:
that a file has no fields.

NAT2813: Objects without subobjects listed successfully.

Text
Objects without subobjects listed successfully.
Explanation
At RETRIEVAL, all objects having no relation to a subobject
were requested. These objects have been displayed successfully.

NAT2814: Too many continuation cards. Input skipped:

Text
Too many continuation cards. Input skipped:
Explanation
The command input for Predict in batch is delimited. Under special
circumstances some input cards are skipped. The skipped parameters
are listed.
Action
Reduce command input.

NAT2815: Overflow occurred. Parameter possibly skipped:

Text
Overflow occurred. Parameter possibly skipped:
Explanation
The command input for Predict in batch is delimited. Under some
circumstances an overflow may have occurred and not all parameters
are recognized by the command processor. The skipped parameters are
listed.
Action
Reduce command input in batch.

NAT2816: Error description displayed.

Text
Error description displayed.
Explanation
In the command line a help request was entered. The error description
for the requested error has been displayed.

NAT2817: Command help displayed.

Text
Command help displayed.
Explanation
In the  command line a help request was entered. The help description
will be displayed.

NAT2818: Internal error in command processor.

Text
Internal error in command processor.
Explanation
An internal error has occurred.
Action
Document the command sequence and contact SAG support.

NAT2819: Object converted.

Text
Object converted.
Explanation
The conversion of an object from version 1 format into version 2
format was executed.

NAT2820: Object has got an old description.

Text
Object has got an old description.
Explanation
Before the conversion is started an old description for the object
has been found.

NAT2821: Object has got a new description.

Text
Object has got a new description.
Explanation
Before the conversion is started a description in version 2 format
has been found.
Action
Delete the new description or do not start the conversion.

NAT2822: Object conversion listed successfully.

Text
Object conversion listed successfully.
Explanation
The converted objects have been displayed successfully.

NAT2823: For object class 'ALL' no ID allowed.

Text
For object class 'ALL' no ID allowed.
Explanation
No identification (ID) may be defined when all data of the dictionary
should be unloaded or when all unloaded data on the sequential data
set should be loaded.
Action
Do not specify any ID when using the command 'ALL'.

NAT2824: System points to a different library.

Text
System points to a different library.
Explanation
The program implementation pointer consisting of
        - program id
        - library
        - fnr
        - dbid
is not equivalent to the implementation pointer of the system which
the program belongs to. The system implementation consists of
        - library id
        - fnr
        - dbid.
Action
Change the implementation pointer of the program.

NAT2825: Keys must be different.

Text
Keys must be different.
Explanation
The specified keywords for an object must be different.
Action
Check specified keys.

NAT2826: Synonyms must be different.

Text
Synonyms must be different.
Explanation
The specified synonyms for an element must be different.
Action
Enter different synonyms.

NAT2827: PF-KEY must be less than 25.

Text
PF-KEY must be less than 25.
Explanation
Predict supports PF-KEY 1 thru PF-KEY 24.
Action
Enter a valid PF-KEY.

NAT2828: Maximum page size is 250.

Text
Maximum page size is 250.
Explanation
The specified page size must be less 251.
Action
Enter a valid page size.

NAT2829: Synonym must be 1...9.

Text
Synonym must be 1...9.
Explanation
Up to 9 synomyms can be specified.
Action
Use only synonym1 thru synonym9.

NAT2830: This user is not defined or was purged.

Text
This user is not defined or was purged.
Explanation
The specified user is not known in Security. For details, consult the
Natural Security documentation and the security notes in the Predict
Reference documentation.

NAT2831: Invalid password entered.

Text
Invalid password entered.
Explanation
An invalid password was entered. Either an unauthorized user tried to
violate the system or the password was misspelled. For details, consult
the Natural Security documentation and the security notes in the
Predict documentation.
Action
Enter the correct password.

NAT2832: The user is not an authorized owner.

Text
The user is not an authorized owner.
Explanation
An attempt was made to execute a function with an object for which the
user must be an authorized owner. For details, see the Natural Security
documentation and the security notes in the Predict documentation.

NAT2833: No authorized owners signed with passwords.

Text
No authorized owners signed with passwords.
Explanation
An authorized owner must sign with his password when a function is
performed on an object not belonging to the user. For details,
see the Natural Security documentation and the security notes in the
Predict documentation.

NAT2834: Authorized owners must sign.

Text
Authorized owners must sign.
Explanation
If a function is to be performed on an object not belonging to the
user and the user is linked to that object, authorized owners
must sign with their passwords. For details, see Natural Security
documentation and the security notes in the Predict documentation.

NAT2835: User not authorized to generate this DDM.

Text
User not authorized to generate this DDM.
Explanation
In Natural Security the user is not authorized to generate the Data
Definition Module. For details, see the Natural Security documentation
and the security notes in the Predict documentation.

NAT2836: No 'SCRATCH' because of activated user-exit.

Text
No 'SCRATCH' because of activated user-exit.
Explanation
If the user-exit for the purge function is activated, 'SCRATCH' of
objects is not possible any longer.
Action
Use the 'PURGE' function.

NAT2837: Not enough owners available.

Text
Not enough owners available.
Explanation
This message occurs during the purge of an Adabas file, if Security
is active. Predict determines the minimum number of security owners
of the DDMs related to this Adabas file. For every DDM the owners
must sign. Sometimes it might happen, that the established list is
not sufficient for Natural Security. In this case, please purge
first all related user views and then the Adabas file.
Action
Delete the userviews.

NAT2838: Renumber not allowed for user views.

Text
Renumber not allowed for user views.
Explanation
The function renumber is not allowed for files of type 'U' (Userview).
Action
Renumber the Adabas file.

NAT2839: No line marked with '.N'.

Text
No line marked with '.N'.
Explanation
The edit command 'POINT' only makes sense, if a line has been marked
with '.N' before.
Action
Mark a line with '.N' before issuing the edit command 'POINT'.

NAT2840: The fields related to the standard file have been listed.

Text
The fields related to the standard file have been listed.
Explanation
All fields related to the standard file have been displayed
on the screen.

NAT2841: File number required.

Text
File number required.
Explanation
The specification of the file number is required.
Action
Enter a file number.

NAT2842: File is not a VSAM file.

Text
File is not a VSAM file.
Explanation
The referenced file is not a VSAM file.
Action
Check input and correct error.

NAT2843: Logical VSAM files only for 'KSDS' files.

Text
Logical VSAM files only for 'KSDS' files.
Explanation
The creation of logical VSAM files are only allowed if the
physical file is of type 'KSDS'.
Action
Check file type.

NAT2844: No library specified.

Text
No library specified.
Explanation
A member and a library must be specified for the PUNCH command.
Action
Enter a library.

NAT2845: Related File number only allowed for logical VSAM files.

Text
Related File number only allowed for logical VSAM files.
Explanation
If you add a new file the specification of the related file number
is only allowed for logical VSAM files.
Action
Enter blank for related file number.

NAT2846: Member punched out on work file 1.

Text
Member punched out on work file 1.
Explanation
The member specified was punched out on work file 1.

NAT2847: Number of lines processed.

Text
Number of lines processed.
Explanation
This message informs the user how many lines were processed.

NAT2848: File number must change.

Text
File number must change.
Explanation
If you change the file type of a userview, the file number must
be changed too.
Action
Enter a new file number.

NAT2849: Object not unique.

Text
Object not unique.
Explanation
The truncated object name, which was checked by the command-processor,
is not unique.
Action
Correct error.

NAT2850: Do not modify standard attributes.

Text
Do not modify standard attributes.
Explanation
The currently modified field contains standard attibutes.
You may not modify those standards unless you mark the field as
nonstandard.
Action
Enter the correct attribute or mark the field as nonstandard.