Natural System Error Messages 6201-6250

NAT6201: Initializing application-independent variables caused an error.

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.

NAT6202: Error processing nested database loop in multi-fetch mode.

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).

NAT6203: A domain error occurred in an arithmetic function.

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.

NAT6204: An argument singularity error occurred in an arithmetic function.

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.

NAT6205: Overflow occurred in an arithmetic function.

Text
Overflow occurred in an arithmetic function.
Explanation
The result of the function is too large to be represented.
Action
Correct error in program.

NAT6206: A partial loss of significance occurred in arithmetic function.

Text
A partial loss of significance occurred in arithmetic function.
Action
Correct error in program.

NAT6207: A total loss of significance occurred in an arithmetic function.

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.

NAT6208: Underflow occurred in an arithmetic function.

Text
Underflow occurred in an arithmetic function.
Explanation
The result of the function is too small to be represented.
Action
Correct error in program.

NAT6209: Calling object no longer available when the call was returned.

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.

NAT6210: Initializing a global data area caused an internal error.

Text
Initializing a global data-area caused an internal error.
Explanation
Internal error.
Action
Contact Software AG support.

NAT6211: Do not use DYNAMIC direction change in multi-fetch mode.

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.

NAT6212: No more memory is available. Stack of subtasks has overflowed.

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.

NAT6213: No more memory available to process request for input or output.

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.

NAT6214: No more memory is available to process a CALL statement.

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.

NAT6215: The RET function applies only to programs that have been called.

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.

NAT6216: PF keys are set on too many levels of a program.

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.

NAT6217: Processing an error at runtime caused an error in the processing.

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.

NAT6218: Text for months of the year not available in current language.

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.

NAT6219: Text for days of the week not available in the current language.

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.

NAT6220: Internal error when reading work file.

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.

NAT6221: Internal error when writing work file.

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.

NAT6222: Fields in a WRITE WORK FILE statement too long.

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.

NAT6223: A numeric field contains a non-numeric digit.

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.

NAT6224: Internal error during loop processing.

Text
Internal error during loop processing.
Action
Contact Software AG support.

NAT6225: Internal error during AT BREAK processing.

Text
Internal error during AT BREAK processing.
Action
Contact Software AG support.

NAT6226: Internal error during RETRY processing.

Text
Internal error during RETRY processing.
Action
Contact Software AG support.

NAT6227: Internal error.

Text
Internal error.
Action
Contact Software AG support.

NAT6228: Internal error during processing of program levels.

Text
Internal error during processing of program levels.
Action
Contact Software AG support.

NAT6229: Internal error during processing of program levels.

Text
Internal error during processing of program levels.
Action
Contact Software AG support.

NAT6230: Internal error during loop processing.

Text
Internal error during loop processing.
Action
Contact Software AG support.

NAT6231: Internal error during loop processing.

Text
Internal error during loop processing.
Action
Contact Software AG support.

NAT6232: Internal error during processing of program levels.

Text
Internal error during processing of program levels.
Action
Contact Software AG support.

NAT6233: Internal error during processing of program levels.

Text
Internal error during processing of program levels.
Action
Contact Software AG support.

NAT6234: Internal error during processing of program levels.

Text
Internal error during processing of program levels.
Action
Contact Software AG support.

NAT6235: Internal error during processing of operation stack.

Text
Internal error during processing of operation stack.
Action
Contact Software AG support.

NAT6236: Internal error in interface to database server.

Text
Internal error in interface to database server.
Action
Contact Software AG support.

NAT6237: Attempt to execute a database call to undefined database type.

Text
Attempt to execute a 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 NATPARM utility.
2. Recatalog the Natural programs if the
   database assignment has changed.
Action
See explanation

NAT6238: Attempt to execute a database call to undefined database type.

Text
Attempt to execute a 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 NATPARM utility.
2. Recatalog the Natural programs if the
   database assignment has changed.
Action
see explanation

NAT6239: Internal error in interface to database server.

Text
Internal error in interface to database server (replacement table).
Explanation
Internal error.
Action
Contact Software AG support.

NAT6240: FETCH not allowed when dialogs are active.

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.

NAT6241: Parameter access failed (not passed).

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.

NAT6242: Value too large for index of dimension :1: (help on array field).

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.

NAT6243: CALLNAT from extern (3GL): too many parameters specified.

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.

NAT6244: Internal memory handling error.

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.

NAT6245: Internal error: name :1: code :2: subcode :3:

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.

NAT6246: Invalid usage of ODA (Object Data Area).

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.

NAT6247: Inconsistent structure of ODA in CLASS and METHOD.

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.

NAT6248: Inconsistent structure of OPS in runtime and compiler

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.

NAT6249: Internal Error during *LENGTH evaluation

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.

NAT6250: Tried to apply a wrong value to *LENGTH

Text
Tried to apply a wrong value to *LENGTH
Explanation
The system variable *LENGTH may be modified in order to increase the
used size of a dynamic variable. The following conditions must be kept,
when *LENGTH is modified:

1. *LENGTH must not be set to a negative value
2. *LENGTH must not be set to a higher value than the allocated data
   space
Action
Check the conditions mentioned above.
The Natural EXPAND statement may be used to increase the data space of
a dynamic variable.