Text |
Abnormal end due to unhandled LE condition .... |
Explanation |
During the execution of an LE (IBM Language Environment) subprogram, an error condition has occurred. As no condition handler was active in the subprogram to handle the error, control has been passed to the Natural LE condition handler, which calls LE services to write an LE snap dump to CEEDUMP and to issue more detailed LE error messages. |
Action |
Check the LE error condition, the messages and the snap dump to find out the reason of the error. If necessary, correct the LE subprogram. |
Text |
Normal end of execution. |
Explanation |
This message indicates the successful execution or completion of a Natural batch job. |
Action |
No action required. |
Text |
Database loop processing limit exceeded. |
Explanation |
The processing limit of a HISTOGRAM/FIND/READ database loop is
specified via a numeric constant or a numeric user-defined variable.
When this limit is exceeded, this does not necessarily indicate an
error condition; however, the records which met the search criteria
in a database loop but which are beyond the limit have not been
processed.
Note: The general limit for processing loops may also be set with the
Natural session parameter LT.
|
Action |
Increase the limit value or ignore this error message. |
Text |
Time limit exceeded. |
Explanation |
In TP mode, this message means that the time-out parameter specified for the TP monitor at system generation time is not sufficient to handle current program requirements. In batch mode, after determining that the program is not in an endless loop, the MT parameter (via a SET GLOBALS statement or GLOBALS command) can be used to increase the CPU-time factor. |
Action |
Check program and correct it if necessary. If program is correct, contact your Natural administrator. |
Text |
Abnormal termination ... during program execution. |
Explanation |
An abnormal termination has occurred during the execution of a Natural object program. A common cause of this error is the use of an arithmetic operand which does not contain valid numeric data at execution time. |
Action |
Check program and correct error. |
Text |
Abnormal termination ... during program compilation. |
Explanation |
An internal abnormal termination has occurred during the Natural syntax/compilation phase. |
Action |
Contact your Natural administrator. |
Text |
Abnormal termination ... during command analysis. |
Explanation |
An abnormal termination of the Natural system has occurred during the evaluation of a command. |
Action |
Contact your Natural administrator. |
Text |
Database loop limit reached with "LE=ON". |
Explanation |
The limit specified for a database processing loop in a FIND, READ or HISTOGRAM statement was reached. This leads to a termination of the loop statement and the program flow continues normally with the statement following the aborted loop. At the end of the program, error message NAT0957 is encountered, if parameter "LE=ON" is set. The limit may be either set with an explicit value supplied in the database loop statement (e.g. FIND (10) ..) or, if no explicit limit was given, globally in a program with the LIMIT statement (e.g. LIMIT 10). In batch mode, Natural will continue processing only if the session parameter CC is set to "OFF". |
Action |
Increase the limit value or set "LE=OFF". |
Text |
Invalid usage of ODA (object data area) in method .... |
Explanation |
Object data areas (ODAs) are defined in methods to use class-specific data. If an ODA is defined in a subprogram, this subprogram can only be called as a method of a class (statement SEND METHOD). Also the ODA defined in a method must be compatible to the ODA defined in the class. The method is either being called without using SEND METHOD, or the ODA defined in the method contains a different number of variables than the ODA defined in the class. |
Action |
Activate the method using SEND METHOD. Ensure that the ODA defined in the method contains the same number of variables as the ODA defined in the class. |
Text |
Inconsistent ODA structure in class ... and method ... (...). |
Explanation |
Object data areas (ODAs) are defined in methods to use class-specific data. Therefore, the structure of the ODA defined in the class must match the structure of the ODA defined in the method. An inconsistency was detected for the variable shown in brackets. |
Action |
Ensure that the variables contained in the ODA of a method and its class have the same format and length. |
Text |
SAVE/CATALOG/PURGE/UNCATALOG terminated unsuccessfully. |
Explanation |
The operation was attempted repeatedly and a response code of "9" for transaction back-out was received from Adabas when XREF data were processed. |
Action |
Ask your Natural administrator to review the maximum transaction duration time setting for Adabas. |
Text |
Concurrent SAVE/CAT/PURGE/UNCAT; or hold queue full. |
Explanation |
The same source program/object module is currently being processed for update by another user. This error condition can also be produced when Adabas response code "145" is received while attempting to delete the "old" copy of the Natural source or object program. A common reason for this error is an overflow of the Adabas hold queue. |
Action |
Retry operation later. If problem persists, notify your Natural administrator. |
Text |
Invalid access to Natural system library. |
Explanation |
An attempt was made to access/replace a program in the Natural system library "SYSLIB". The use of "SYSLIB" is restricted to Natural system routines; a user must not use library ID "SYSLIB". |
Action |
Do not attempt to access the system library "SYSLIB". |
Text |
Security violation during program execution (...). |
Explanation |
The current user has attempted to execute a Natural program which has a restricted status. |
Action |
Contact your Natural administrator. |
Text |
Subroutine/Function ... already exists as member .... |
Explanation |
Names of subroutines/functions within a library must be unique. |
Action |
Choose another name for the subroutine/function. |
Text |
Conversion error returning RESULT parameter :1: (:2: :3:/:4:/:5:/:6:) |
Explanation |
While returning the value of parameter :1:, which was defined with the attributes BY VALUE RESULT in object :3: (of type :2:, loaded from library :4: from database :5: file number :6:), a conversion error has occurred. Check if the current value complies with the "Rules for Arithmetic Assignment" described in the Natural documentation. |
Action |
Correct error in program. |
Text |
Convs. error assigning BY VALUE parameter :1: (:2: :3:/:4:/:5:/:6:) |
Explanation |
During assignment of the value of parameter :1:, which is defined with the attributes BY VALUE (RESULT) in object :3: (of type :2:, loaded from library :4: from database :5: file number :6:), a conversion error has occurred. Check if the current value complies with the "Rules for Arithmetic Assignment" described in the Natural documentation. |
Action |
Correct error in program. |
Text |
Function ... not permitted in current context. |
Explanation |
The function indicated is not permitted in a certain context, e.g. while the 3GL callnat interface, a SEND METHOD or a PARSE is active. |
Action |
Correct error in program. |
Text |
Mandatory parameter ... not specified (... .../.../.../...) |
Explanation |
The parameter, which is not specified as optional in the PDA, was not passed. The called object is described by type, name, database ID, and file number. This error can occur also if too few parameters are passed. |
Action |
Check program and correct the error. |
Text |
Dynamic parameter :1: mismatch (:2: :3:/:4:/:5:/:6:). |
Explanation |
The parameter defined at position :1: in object :3: (of type :2:, loaded from library :4:, database :5:, file number :6:) does not match with the corresponding parameter used to invoke it. The parameters, which are used by reference, must be either dynamic in both caller and declaration, or non-dynamic in both caller and declaration. |
Action |
Check programs and correct the error. |
Text |
Source line limit for program creation is zero. |
Explanation |
When the security authorization for this user in this application was defined, the user was allowed to create source programs but the limit for the number of source lines to be created was erroneously set to "0". |
Action |
Contact your Natural Security administrator. |
Text |
Source line limit reached. |
Explanation |
In the security authorization for this user in this application, a limit of source lines to be created in new programs has been defined. The user cannot exceed this limit when creating new programs. |
Action |
Either reduce program size or ask your Natural Security administrator to increase the limit of source lines. |
Text |
User is not authorized to use this command: .... |
Explanation |
In the security authorization for this user in this application, only specific commands have been made available. The user is not allowed to use the command specified. |
Action |
Do not use this command in this environment, or contact your Natural Security administrator for authorization. |
Text |
User is not authorized to use this statement. |
Explanation |
In the security authorization for this user in this application, only certain statements have been made available. The user is not allowed to use the specified statement. |
Action |
Do not use this statement, or ask your Natural Security administrator for authorization. |
Text |
User is not authorized to use this file. |
Explanation |
In the security authorization for this user in this application, only certain files have been made available. The user is not allowed to use the specified file. |
Action |
Either do not use this file or contact your Natural Security administrator for authorization. |
Text |
User is not authorized to update this file. |
Explanation |
In the security authorization for this user in this application, only certain files have been made available for updating. The user is not allowed to update the specified file. |
Action |
Do not update this file, or contact your Natural Security administrator for authorization. |
Text |
Inconsistent security definition for command selection. |
Explanation |
An inconsistent definition may occur if the Natural administrator has selected commands on the selection screen in the Natural Security system that are not defined to the system. |
Action |
Contact your Natural administrator. |
Text |
Inconsistent security definition for statement selection. |
Explanation |
An inconsistent security definition may occur if the Natural administrator selects statements that are not defined to the system. |
Action |
Contact the Natural administrator. |
Text |
Invalid use of default format definition (N7). |
Explanation |
Natural Security allows specification of the user characteristics; one option of these is whether the user is allowed to use the default format definition (N7). For this user in this application, the option is not allowed. |
Action |
You must explicitly specify the format/length of variables. |
Text |
Specification of the library not allowed. |
Explanation |
In a security-protected environment, a user may not access a library by merely specifying the library ID in a command. The user must properly log on to the library and may then access it. This protection is also valid in a non-security environment for a library ID that starts with "SYS". |
Action |
Log on to the desired library and then re-issue the command. |
Text |
Invalid use of database file number. |
Explanation |
The use of a file number in a database access statement is not allowed. |
Action |
Use the view name instead of a file number. |
Text |
Use of 2-character database short-name field not allowed. |
Explanation |
A reference to a 2-character database short-name field is not permitted, 1)- when running under Natural Security; 2)- inside the definition of a data-view (DEFINE DATA); 3)- when a DEFINE DATA LOCAL was previously used to define variables; 4)- when the compiler option DBSHORT=OFF is set. |
Action |
Do not use 2-character database short-name fields. |
Text |
Internal error; invalid system command requested. |
Explanation |
A system command was requested that requires a Natural program which is not defined. |
Action |
Contact your Natural administrator. |
Text |
Update commands not authorized by Natural Security. |
Explanation |
You are not allowed to issue update commands. |
Action |
Contact your Natural administrator concerning Natural Security definition/authorization. |
Text |
This file is not defined in Natural Security. |
Action |
Check program and correct error, or contact your Natural Security administrator. |
Text |
Return value not defined in function ... (.../.../...). |
Explanation |
A return value is required by the calling object, but not defined in the called function. The name of the function, its library, DBID and FNR are indicated in the error message. |
Action |
Check program and correct error. |
Text |
Format/length conflict in return variable (.../.../.../...). |
Explanation |
The return variable specified in the DEFINE PROTOTYPE statement is defined with a format/length different from that of the corresponding return variable defined in the called function. The name of the function, its library, DBID and FNR are indicated in the error message. |
Action |
Check program/function and correct error. |
Text |
Conversion error in BY VALUE variable (.../.../.../...). |
Explanation |
While returning the value of a return variable which is defined with the attribute BY VALUE in a function, a conversion error has occurred. Make sure that the value specified in the DEFINE PROTOTYPE statement matches the "Rules for arithmetic assignment" described in the Natural documentation. The name of the function, its library, DBID and FNR are indicated in the error message. |
Action |
Correct error in program. |
Text |
Dynamic return variable mismatch (.../.../.../...). |
Explanation |
A return variable which is used by reference must be either dynamic in both the DEFINE PROTOTYPE statement and the function declaration, or non-dynamic in both the DEFINE PROTOTYPE statement and the function declaration. The name of the function, its library, DBID and FNR are indicated in the error message. |
Action |
Check program/function and correct error. |
Text |
Parameter format not allowed for call from 3GL. |
Explanation |
A Natural subprogram which is invoked from a third-generation language like Cobol, PL/I, or C, cannot use parameters defined as DYNAMIC variable, X-array, or variable array (1:V). |
Action |
In a Natural subprogram to be invoked from a 3GL, define as parameters only static variables and arrays with fixed index bounds. |
Text |
Invalid format buffer for STORE/UPDATE statement. |
Explanation |
Natural has detected a format buffer for a STORE/UPDATE statement with a length of zero. This is invalid. |
Action |
Check program and correct error. |
Text |
Internal error .... |
Action |
Contact your Natural administrator. |
Text |
Internal error. |
Action |
Contact your Natural administrator. |