Text |
Restart program ... cannot be found. |
Explanation |
The restart program specified in the security profile of the library used cannot be found, neither in the library itself nor in any steplib. |
Action |
Contact your Natural Security administrator. |
Text |
Error program ... cannot be found. |
Explanation |
The error program specified - either in the security profile of the library used or with the parameter ETA - cannot be found, neither in the library itself nor in any steplib. |
Action |
Contact your Natural Security administrator. |
Text |
Incomplete security profile; call security administrator. |
Explanation |
Either you are defined to Natural Security as a user of type MEMBER. Users of this type must be contained in at least one group. You have not been added to any group, or your user type should be changed. Or your terminal is defined to Natural Security, but is not contained in any group. |
Action |
Contact your Natural Security administrator. |
Text |
Logon accepted to library .... This library is empty. |
Action |
No action required. |
Text |
Logon accepted to library .... |
Action |
No action required. |
Text |
New password must be at least ... characters long. |
Explanation |
Natural Security requires that passwords have a minimum length. |
Action |
Choose a longer password. |
Text |
Automatic logon with invalid logon data; logon failed. |
Action |
Contact your Natural Security administrator. |
Text |
This user is currently locked. |
Action |
Contact your Natural Security administrator. |
Text |
Format of expiration date must be as in top right corner. |
Explanation |
The expiration date for a mailbox must be entered in the same format as the date displayed in the top right hand corner of the screen. |
Action |
Enter valid expiration date in valid format. |
Text |
Expiration date may not be a date in the past. |
Action |
Enter a valid date. |
Text |
Invalid code. |
Action |
Enter valid code. |
Text |
User has no special link to library. |
Action |
Contact your Natural Security administrator. |
Text |
This Natural session is not under Natural Security. |
Explanation |
In order to perform the desired function, your Natural session must be running under Natural Security. |
Action |
Invoke Natural under Natural Security (ask your Natural administrator if necessary) before you perform the desired function. If Natural Security is not installed, that function is not available. |
Text |
Logon to this library not allowed via link ID "...". |
Action |
Log on with a valid user ID; contact your Natural Security administrator if necessary. |
Text |
No. Lib. ID Library Name*Type*Linked via*Spec. |
Explanation |
Text displayed by Natural Security. |
Text |
Invalid security file. Please contact your DBA. |
Action |
Contact your database administrator. |
Text |
Your Natural nucleus is not a Natural Security nucleus. |
Explanation |
There is an inconsistency between your Natural nucleus and your Natural system file (FNAT). The nucleus is marked as non-Security, but the Natural system file contains Natural Security-specific programs. Possible reasons for this inconsistency are: - the nucleus has been illegally zapped. - the Natural master control record has been illegally zapped. - the Natural Security NATLOAD has not been performed successfully. |
Action |
Contact your Natural administrator. Repeat the NATLOAD for Natural, and - if your system is a Natural Security one - also repeat the NATLOAD for Natural Security. |
Text |
Mailbox does not exist / not assigned to your environment. |
Action |
Choose another mailbox ID; or contact your Natural Security administrator. |
Text |
The expiration date of mailbox ... is already reached. |
Action |
If necessary, change the expiration date. |
Text |
The file security record has been directly manipulated. |
Action |
Contact your Natural Security administrator. |
Text |
Upload is not permitted. |
Action |
Contact your Natural Security administrator. |
Text |
Download is not permitted. |
Action |
Contact your Natural Security administrator. |
Text |
Invalid function code. |
Action |
Enter valid function code. |
Text |
User ID or password invalid. |
Action |
Enter correct user ID and correct password. |
Text |
Press ENTER for next page, or "." to terminate session. |
Text |
This user is currently not active. |
Action |
Contact your Natural Security administrator. |
Text |
New password is not valid. Please choose a different one. |
Explanation |
The new password was denied for one of the following reasons: 1) The new password is too similar to previous passwords. 2) The new password does not conform to the rules for passwords. |
Action |
Contact your Natural Security administrator. |
Text |
Utility ... access denied by Security. Contact your DBA. |
Explanation |
The utility is for restricted use only. |
Action |
Please contact your security administrator. |
Text |
Assigned group ... is currently not active. |
Explanation |
In a Natural Security (NSC) environment: - The NSC group ID shown in the message is defined with a date which marks this group ID as currently inactive. Additional information for NSF environments: - The group ID, for the user ID defined in the security system, is not defined in NSC, or the NSC group profile is inactive, or the NSC user profile is of another user type. |
Action |
Contact your Natural Security administrator. |
Text |
No active group assigned. |
Explanation |
The user is not assigned to a group with a valid activation date. |
Action |
Contact your Natural Security administrator. |
Text |
More than 10 syntax errors occurred in BATCH compile. |
Action |
Correct syntax errors and re-compile. |
Text |
During compilation, the internal ... table exceeds ... maximum. |
Explanation |
During compilation of a program, various tables are generated to build the object. One of these tables exceeds its maximum size. Identification list: GPT - Generated program buffer KST - Constant buffer MPT - Array structure buffer RNM - SQL generation buffer SBT - Database access buffer VAT - SQL generation buffer VDT - Variable access buffer |
Action |
According to the buffer identification, the program must be reduced in size. |
Text |
Internal error, save area chain destroyed. |
Explanation |
The relocatable save area in Natural is destroyed. Natural resets the chain and restarts. Natural always tests the correct chains of its save areas. The error is caused by a wrong register 13, a save area overflow, or a wrong relocated user area. One reason for a save area overflow may be too many recursive program calls. |
Action |
Natural corrects automatically and restarts. If need be, reduce the number of recursive program calls. |
Text |
Internal error, I/O buffer overwritten. |
Explanation |
The buffer area that is used to generate output to the screen/printer is also used for other purposes. A condition has arisen where the contents of this I/O buffer have been destroyed, and the buffer has not been re-initialized. |
Action |
Note down the command sequence and contact your Natural administrator. |
Text |
Storage overflow in extended buffer. |
Explanation |
Certain tables during processing and compilation of Natural programs are stored in the extended buffer. The size of the extended buffer is defined by the Natural administrator with the ESIZE profile parameter. This error may also be caused by an attempt to write too many data to the Natural stack. |
Action |
Reduce size of source program, or contact your Natural administrator. |
Text |
Internal stack overflow. |
Explanation |
During a stack operation into the runtime buffer a table overflow occurred. This situation should never occur and is probably caused by an (incorrect) excessive store in a runtime buffer table. |
Action |
Ask your Natural administrator to increase the RUNSIZE parameter; if problem persists, contact Software AG Natural support. |
Text |
Storage overflow during compilation or execution. |
Explanation |
This error is caused by an overflow situation: - At compilation time, this error is issued if the length of an arith- metic expression in an IF condition exceeds the maximum of 32 KB. - At execution time, this error is due to a relocation of the DATSIZE buffer at execution of a Natural subprogram from a 3GL program (Natural 3GL program interface). |
Action |
Compilation: Reduce the number of arithmetic operations
in the condition.
Execution: Use the CALLNAT interface INTERFACE4.
|
Text |
Invalid source parameter construction. |
Explanation |
A possible cause for the error is the construction of a parameter source notation within another source parameter. Natural supports only one level of parameter source processing. |
Action |
Check program and correct error. |
Text |
Natural symbol table exceeds maximum size of 512K. |
Explanation |
During compilation, symbols in a program are covered in a buffer, called symbol table (SYT). The maximum size of the SYT (512K) overflows. |
Action |
Reduce the number of variables in the program and recompile. |
Text |
Maximum statement length exceeded |
Explanation |
A single Natural statement must not exceed 64KB in length. |
Action |
Reduce the statement length. |
Text |
Invalid format/length for operand. |
Explanation |
An invalid format/length definition is used for an operand. This can have the following reasons: MINVAL/MAXVAL: The combination of operands with their format/length definitions does not comply with the rules for the generation of intermediate formats. Use the IR clause to set a certain format/length as result. |
Action |
Change the format/length of the operands. |
Text |
GFID validation error (reason/LDA-name/view-name/field-name). |
Explanation |
During the generation of a global format ID (GFID) for a
database-access statement, a validation error was encountered,
because a view-field definition was changed in the DDM, but the LDA
containing the view was not recataloged.
Reason codes:
4: DB short name was changed.
8: Field format was changed.
12: Field length was changed.
16: Total view length is different.
20: Inconsistent LDA image found, delete LDA from buffer pool and
catalog again.
|
Action |
Recatalog the specified LDA, or set GFID=OFF with a COMPOPT command or OPTIONS statement so that GFIDs are not used. |
Text |
Internal error in structure of DDM .... |
Explanation |
The DDM was not correctly generated and contains an internal inconsistency. |
Action |
Re-generate the DDM. |