Text |
Cannot insert global or application-independent variables. |
Explanation |
This error can have two causes: a) out of memory b) table overflow Either the operating system is not configured correctly or there is not enough space on the disc for the system swapfile. All descriptions of application-independent variables are collected in a table of limited size. The table can overflow if an extremely large number of application-independent variables is created. The same situation applies to context variables. Check the configuration settings of the operating system and correct them if neccessary. Then check the available disk space for your system swapfile. Check the number of application-independent and context variables. |
Action |
Check the number of application-independent and context variables. Contact your system administrator. |
Text |
Initializing application-independent variables caused an error. |
Explanation |
Natural has encountered an internal error. It can also occur with context variables" initialization. |
Action |
Contact Software AG support. |
Text |
Error processing nested database loop in multi-fetch mode. |
Explanation |
In a nested database-access loop, a database-modification statement attempts to modify a file that is read by an outer loop. |
Action |
Make sure that multi-fetch processing is switched off in the outer database loop(s). |
Text |
A domain error occurred in an arithmetic function. |
Explanation |
An argument to the function is outside the domain of the function. The
function was called with an invalid floating-point operand.
|
Action |
Correct error in program. |
Text |
An argument singularity error occurred in an arithmetic function. |
Explanation |
An argument to the function has an illegal value (for example, the value zero is passed to a function that requires a non-zero value). |
Action |
Correct error in program. |
Text |
Overflow occurred in an arithmetic function. |
Explanation |
The result of the function is too large to be represented. |
Action |
Correct error in program. |
Text |
A partial loss of significance occurred in arithmetic function. |
Action |
Correct error in program. |
Text |
A total loss of significance occurred in an arithmetic function. |
Explanation |
The result of the function will be inaccurate. |
Action |
Correct error in program. |
Text |
Underflow occurred in an arithmetic function. |
Explanation |
The result of the function is too small to be represented. |
Action |
Correct error in program. |
Text |
Calling object no longer available when the call was returned. |
Explanation |
An object has been called and has completed its processing. Processing cannot return to the the object which called it, because that object is available neither in the bufferpool nor in a library. |
Action |
Put the calling object, in cataloged form, into the current library, the system-library or the step library. |
Text |
Initializing a global data-area caused an internal error. |
Explanation |
Internal error. |
Action |
Contact Software AG support. |
Text |
Do not use DYNAMIC direction change in multi-fetch mode. |
Explanation |
The dynamic direction change can only be used when the corresponding processing loop is not executed in multi-fetch mode. |
Action |
Use a VARIABLE direction clause instead of a DYNAMIC direction clause if possible; or switch off multi-fetch mode for this statement with the MULTI-FETCH OFF clause. |
Text |
No more memory is available. Stack of subtasks has overflowed. |
Explanation |
Either the operating system is not configured correctly or there is not enough space on the disc for the system swap file. |
Action |
Please contact your Administrator. |
Text |
No more memory available to process request for input or output. |
Explanation |
Either the operating system is not configured correctly or there is not enough space on the disc for the system swapfile. Check the configuration settings of the operating system and correct them if neccessary. Then check the available disk space for your system swapfile. |
Action |
Please contact your system administrator for further help. |
Text |
No more memory is available to process a CALL statement. |
Explanation |
Either the operating system is not configured correctly or there is not enough space on the disc for the system swapfile. Check the configuration settings of the operating system and correct them if neccessary. Then check the available disk space for your system swapfile. |
Action |
Please contact your system administrator for further help. |
Text |
The RET function applies only to programs that have been called. |
Explanation |
The RET function was applied to a program that had not been called. |
Action |
Either insert a CALL to the program before the RET function, or remove the RET function. |
Text |
PF keys are set on too many levels of a program. |
Explanation |
A structure is allocated to every level of a program where PF keys (program function keys) are set. All the structures for one program must fit in a segment of 64K. The structure for the current level does not fit in the segment for the current program. |
Action |
Set PF keys on fewer levels of the program. |
Text |
Processing an error at runtime caused an error in the processing. |
Explanation |
An error has occurred at runtime. Attempts to process the error and display an appropriate message have failed. |
Action |
Contact Software AG support because Natural could have an internal error. |
Text |
Text for months of the year not available in current language. |
Action |
Ask your administrator if the language is available with your installation. If so, the administrator can check whether the appropriate text file is available and reload it, if it is corrupt. |
Text |
Text for days of the week not available in the current language. |
Action |
Ask your administrator if the language is available with your installation. If so, the administrator can check whether the appropriate text file is available and, if it is corrupt, can reload it. |
Text |
Internal error when reading work file. |
Explanation |
There is either a logical error in the work file or a physical error on the disc. |
Action |
Try to write the work file again. If this has no effect, change the disc. |
Text |
Internal error when writing work file. |
Explanation |
There is either a logical error in the work file or a physical error on the disc. |
Action |
Try to write the work file again. If this has no effect, change the disc. |
Text |
Fields in a WRITE WORK FILE statement too long. |
Explanation |
The total length of all the fields in a WRITE WORK FILE statement must be less than about 64K. For portable work files, the limit has been increased to about 2 GB. |
Action |
Apply the WRITE WORK FILE statement to fewer fields or shorter fields. |
Text |
A numeric field contains a non-numeric digit. |
Explanation |
At least one of the digits in a numeric field is not a numeric digit and cannot be processed in a numeric context. |
Action |
Check if the numeric field in question is redefined as alphanumeric or binary. If so, make sure it contains only numeric digits. Otherwise, input data (from the database) could be erroneous. |
Text |
Internal error during loop processing. |
Action |
Contact Software AG support. |
Text |
Internal error during AT BREAK processing. |
Action |
Contact Software AG support. |
Text |
Internal error during RETRY processing. |
Action |
Contact Software AG support. |
Text |
Internal error. |
Action |
Contact Software AG support. |
Text |
Internal error during processing of program levels. |
Action |
Contact Software AG support. |
Text |
Internal error during processing of program levels. |
Action |
Contact Software AG support. |
Text |
Internal error during loop processing. |
Action |
Contact Software AG support. |
Text |
Internal error during loop processing. |
Action |
Contact Software AG support. |
Text |
Internal error during processing of program levels. |
Action |
Contact Software AG support. |
Text |
Internal error during processing of program levels. |
Action |
Contact Software AG support. |
Text |
Internal error during processing of program levels. |
Action |
Contact Software AG support. |
Text |
Internal error during processing of operation stack. |
Action |
Contact Software AG support. |
Text |
Internal error in interface to database server. |
Action |
Contact Software AG support. |
Text |
Attempt to execute database call to undefined database type. |
Explanation |
The database environment which was defined when the Natural programs were catalogued is different from the environment at execution time (e.g., database ID contains a wrong database type). Do one of the following: 1. Change the database assignment in the global CONFIG file and verify that the environment at execution time is the same as it was at catalog time. Use the Configuration utility. 2. Recatalog the Natural programs if the database assignment has changed. |
Action |
See explanation. |
Text |
Attempt to execute database call to undefined database type. |
Explanation |
The database environment which was defined when the Natural programs were catalogued is different from the environment at execution time (e.g., database ID contains a wrong database type). Do one of the following: 1. Change the database assignment in the global CONFIG file and verify that the environment at execution time is the same as it was at catalog time. Use the Configuration utility. 2. Recatalog the Natural programs if the database assignment has changed. |
Action |
See explanation. |
Text |
Internal error in interface to database server (replacement table). |
Explanation |
Internal error. |
Action |
Contact Software AG support. |
Text |
FETCH not allowed when dialogs are active. |
Explanation |
FETCH statements cannot be executed when dialogs are active. |
Action |
Remove the FETCH statement from the offending routine. |
Text |
Parameter access failed (not passed). |
Explanation |
Parameters are optional when they are passed to a dialog or if they are specified with the keyword OPTIONAL in the PDA for a CALLNAT or an external SUBROUTINE. The parameter(s), which have not been passed, cannot be accessed. If an access is tried, this error occurs. This is also true for a redefinition of a parameter. |
Action |
Check the parameter before accessing it. The statements "IF parameter SPECIFIED" or "IF parameter NOT SPECIFIED" can be used for this purpose. |
Text |
Value too large for index of dimension :1: (help on array field). |
Explanation |
Environment, where the error occurrs: Help is requested for an INPUT field, where the field is an element of an array. When the parameters for the helproutine are generated, the indexes of the array element are passed together with the field contents. In this case, each index value must fit into an I2 variable, because the helproutines expect it as an I2. Reason why the error occurs: The given index does NOT fit into an I2 (overflow). |
Action |
Check the value of the index and make sure it will fit into an I2. |
Text |
CALLNAT from extern (3GL): too many parameters specified. |
Explanation |
A CALLNAT from outside of Natural, e.g. from a 3GL program, exceeds the maximum number of supported parameters. Due to performance optimizations, this limit is internally set to 4500. |
Action |
Reduce the number of parameters. If not possible, Contact Software AG support. |
Text |
Internal memory handling error. |
Explanation |
This error is caused by incorrect system administration: a Natural object was changed or removed while Natural was running. That is why information about an active object could not be re-loaded. As the information is required to free active memory, Natural will run out of memory if this error occurs again and again. |
Action |
Shut the Natural session down, restart Natural. Change or remove Natural objects only when no Natural processes are running. |
Text |
Internal error: name ... code ... subcode ... |
Explanation |
Internal error. A name, code, and subcode are contained in the error message. |
Action |
Contact Software AG support and quote the complete error message. |
Text |
Invalid usage of ODA (Object Data Area). |
Explanation |
Object Data Areas are defined in methods to use class specific data. The methods must be activated with the Natural statements CREATE OBJECT and SEND METHOD. An attempt was made to activate a method, which uses an ODA, with a statement other than SEND METHOD (e.g., with the CALLNAT statement). |
Action |
Activate method using the SEND METHOD statement. |
Text |
Inconsistent structure of ODA in CLASS and METHOD. |
Explanation |
Object Data Areas (ODA) are defined in methods to use class specific data. Therefore, the structure of the ODA in the CLASS gp must match the structure of the ODA in a called METHOD. |
Action |
Ensure that the ODAs in CLASS and METHOD have the same number of parameters, format and length. |
Text |
Inconsistent structure of OPS in runtime and compiler |
Explanation |
To support the dynamic operands and operands of type ANY, the compiler has to generate the OPS structure into the gp. This generated OPS structure does not match with the OPS structure that is currently used by the runtime system. |
Action |
Ensure that the catalogued Natural program is version compatible to your currently used Natural version. Recatalogue the Natural program in case of incompatibility, else contact the Software AG Support. |
Text |
Internal Error during *LENGTH evaluation |
Explanation |
The internal structure for the *LENGTH evaluation is not available due to an internal error. |
Action |
Contact the Software AG support. |