Natural System Error Messages 0901-0950

NAT0901: Length of record to be sorted exceeds 10240 bytes.

Text
Length of record to be sorted exceeds 10240 bytes.
Explanation
The total length of the record to be sorted must not exceed
10240 bytes.
Note: The fields written to sort storage are not only
      those fields specified in the SORT statement, but all
      database fields and user-defined variables defined
      before the SORT statement.
Action
Ensure that the sort record does not exceed 10240 bytes.

NAT0902: Generation of format buffer fails. Reason code :1:.

Text
Generation of format buffer fails. Reason code ....
Explanation
During the generation of format buffers, the following error
situation occurred.  Reason code descriptions:
 4 - The generation buffer overflowed and the buffer could
     not be enlarged because there was not enough memory available.
     Ac.==> Start Natural in a larger thread/partition/region.
 8 - Length of generated format buffer exceeds maximum of 32 KB.
     Ac.==> Reduce the number of fields in the format buffer.
12 - At runtime, a format buffer could not be expanded because there
     was not enough memory available.
     Ac.==> Start Natural in a larger thread/partition/region.
16 - At runtime, the storage needed to create the record buffer for a
     MULTI-FETCH database call could not be obtained.
     Ac.==> Start Natural in a larger thread/partition/region.
Action
See reason code descriptions above.

NAT0903: Storage overflow at execution time.

Text
Storage overflow at execution time.
Explanation
Storage overflow while creating a loop-table entry.
Action
Divide program into segments using 'structured programming' techniques.

NAT0904: Too many <MOVE ' ' TO variable> in program.

Text
Too many <MOVE '    ' TO variable> in program.
Explanation
The program contains too many <MOVE '     ' TO variable>
statements.
Action
Replace the statements with <RESET variable>.

NAT0906: Natural nucleus does not support old object code.

Text
Natural Nucleus does not support old object code.
Explanation
Only Natural objects cataloged/stowed with a version supported by this
Natural Runtime version can be processed.
Action
Catalog/stow the Natural object with a newer Natural version.

NAT0907: Generation of record buffer failed. Reason code :1:.

Text
Generation of record buffer failed. Reason code ....
Explanation
During the generation of a database statement, the following error
situation occurred. Reason code description:
4 - Under Natural for Open Systems:
    The record buffer size of an Adabas access statement exceeds 64 KB.
4 - Under Natural for Mainframes:
    The record buffer size of a database access statement directed to
    Adabas Version 7 (or below) or to VSAM exceeds 32 KB.
    A record buffer size greater than 32 KB is only permitted if the
    called database is defined as Adabas V8 (see Profile Parameter DB).
8 - For DB2/SQL access statements the record buffer size exceeds
    the maximum of 32 KB.
Action
Reduce the number of record buffer fields.

NAT0909: Data buffer :1: not expandable while NATXCAL is active.

Text
Data buffer ... not expandable while NATXCAL is active.
Explanation
When a subprogram is invoked via the 3GL interface (NATXCAL, NCIXCALL,
NCIXCPRM), a data buffer cannot be expanded if one of the data fields
residing in this buffer was supplied as a parameter with the CALL
statement that has invoked the 3GL program.
One of the following data buffers may be affected:
AIVDAT  - buffer for AIV variables,
GLBUSER - buffer for user global variables,
GLBSYS  - buffer for system global variables,
DATSIZE - buffer for local variables.
Action
If the buffer indicated is "DATSIZE", start Natural with an
increased value for the DATSIZE profile parameter.

NAT0910: Insufficient space for WRKSIZE to process SORT statement.

Text
Insufficient space for WRKSIZE to process SORT statement.
Explanation
The processing of the SORT statement requires the WRKSIZE buffer whose
size is specified with the NTSORT/SORT profile parameter.
Either WRKSIZE has been set to zero or its value exceeds the available
space in the current thread/partition/region/task (where thread refers
to the Natural thread).
In case of a Natural thread the overflow size OVSIZE is also exceeded
or could not be allocated.
Action
Either decrease WRKSIZE, or start Natural in a larger thread/partition/
region/task, or increase OVSIZE.

NAT0911: :1: incompatible to mainframe version :2: (see :3:).

Text
... incompatible to mainframe version ... (see ...).
Explanation
The statement/keyword used is not compatible with the
corresponding mainframe version of Natural.

You can avoid this error by setting the compatibility switch
referred to in the error message
(e.g., the profile parameter V41MFCOMP=ON/OFF).
Action
Use only compatible statements/keywords,
or switch off the compatibility switch.

NAT0916: Return code :1: from :2: user exit :3:.

Text
Return code ... from ... user exit ....
that caused Natural to discontinue program execution.
Explanation
The user exit detected a condition that prevented the completion of the
operation. The condition has been indicated to Natural by means of a
return code. The return code is specific to the user exit.
Natural program execution has been terminated.
Action
Contact your Natural administrator or the author of the specified user
exit.

NAT0917: Error :1: in :2: :3:.

Text
Error ... in ... ....
Explanation
An error occurred in a statement of a copycode. This message is added
to the initial error to show the object and line of the INCLUDE
statement. In case of nested INCLUDEs, the message is added for each
INCLUDE level. The messages can be displayed with the system command
LASTMSG.
Example:
Program MAIN includes copycode COPYC at line 100.
COPYC calls subprogram SUB1 at line 200. SUB1 does not exists.
- Initial error message:
  COPYC    0200 NAT0923 Invalid program call (Callnat Program SUB1/...
- Additional error message:
  MAIN     0100 NAT0917 Error 923 in Copycode COPYC.
Action
Check program and correct error.

NAT0918: ESCAPE (TOP) not allowed in ON ERROR or AT block.

Text
ESCAPE (TOP) not allowed in ON ERROR or AT block.
Explanation
This error may be caused by one of the following:
1. An ESCAPE statement was used to exit from a currently active
   ON ERROR block. However, an ON ERROR block must be exited with
   a FETCH, STOP, TERMINATE or RETRY statement.
2. An ESCAPE TOP statement was used within one of the following
   conditions:
   - AT BREAK
   - AT START OF DATA
   - AT END OF DATA
Action
Correct error in program.

NAT0919: Too many parameters in CALL statement.

Text
Too many parameters in CALL statement.
Action
Reduce number of parameters in CALL statement.

NAT0920: Program :1: cannot be loaded :2:.

Text
Program ... cannot be loaded ....
Explanation
The specified external program could be neither loaded dynamically nor
located statically. See the supplied operating-system/TP-monitor
return code of the failing LOAD request for details.
Possible reasons:
- The program to be loaded dynamically is not contained in the
  load libraries currently defined to Natural.
- Under CICS: The program is not defined to CICS.
- There was not enough storage available to load the program
  dynamically (under Com-plete: the Com-plete thread was too small).
- The limit for the number of programs to be dynamically loaded
  was exceeded.
- For static programs: the program is not defined in the Natural
  parameter module with the CSTATIC parameter or not linked to the
  Natural parameter module.
Action
Make sure that the program is contained in a library available to
or linked to Natural. Contact your Natural administrator concerning
the setting of the Natural profile parameters CDYNAM and CSTATIC.

NAT0921: Maximum call level reached.

Text
Maximum call level reached.
Explanation
Natural supports calls to other Natural objects up to level 99.
Whenever a Natural object invokes another Natural object
(e.g. via CALLNAT, INPUT MAP, PERFORM, FETCH RETURN), the level counter
*LEVEL is incremented by one. When *LEVEL exceeds 99, this error is
issued.

This error usually occurs when an object calls itself recursively.
Action
Check program and correct error.

NAT0922: Buffer pool not active.

Text
Buffer pool not active.
Explanation
Natural requires an active buffer pool manager.
Action
Contact your Natural administrator.

NAT0923: Invalid program call (:1: :2: :3:/:4:/:5:/:6:).

Text
Invalid program call (:1: :2: :3:/:4:/:5:/:6:).
Explanation
The Natural object :3: (of type :2:, loaded from library :4:,
database :5:, file number :6:) cannot be invoked by statement or
command :1:.
Action
Invoke Natural objects by the appropriate statements/commands.

NAT0924: Command invalid in this context (:1: :2: :3:).

Text
Command invalid in this context (:1: :2: :3:).
Explanation
The command :1: is invalid for object :3: of type :2:.
Action
Consult the documentation and try again.

NAT0925: GDA signature conflict.

Text
GDA signature conflict.
Explanation
This error occurs if a program references a global data area (GDA)
which was recataloged with a changed GDA structure.
If a GDA structure is changed, all objects which reference the GDA
must also be cataloged.
Action
Check the program structure and recatalog. When running on a mainframe
platform, you may use the profile parameter RECAT=ON. RECAT=ON is not
possible for programs cataloged with the Natural Optimizer Compiler.

NAT0926: Compile option GDASC mismatch.

Text
Compile option GDASC mismatch.
Explanation
This error occurs if a program referencing a global data area (GDA)
is cataloged with compile option GDASC=ON and the GDA was
cataloged with compile option GDASC=OFF.
Action
Check the program structure and catalog with compile option
GDASC=OFF, or recatalog the GDA with compile option GDASC=ON.

NAT0927: FETCH RETURN statement rejected by Natural Security.

Text
FETCH RETURN statement rejected by Natural Security.
Explanation
A program called via a FETCH RETURN statement is security protected
and, therefore, cannot be called from another Natural program.
Action
Contact your Natural or Natural Security administrator.

NAT0928: Program can only be executed from a SYS* library.

Text
Program can only be executed from a SYS* library.
Explanation
This program is security protected and can only be executed
from a SYS* library. (SYSTEM is not treated as a SYS* library.)
Action
Log on to the correct library.

NAT0929: Program cannot be executed in batch mode.

Text
Program cannot be executed in batch mode.
Explanation
An attempt was made to execute in batch mode a program that
contains online functions/features.
Action
Execute the program in interactive mode.

NAT0930: Program cannot be executed online.

Text
Program cannot be executed online.
Explanation
An attempt was made to execute in interactive mode a program that
contains functions/features only available in a batch mode environment.
Action
Execute the program in batch mode.

NAT0931: CMSYNIN job control definition is missing.

Text
CMSYNIN job control definition is missing.
Explanation
In batch mode execution, the DD statement for the definition of
the main command and source input for Natural is missing.
No commands can be read.
Action
Specify definition for the CMSYNIN file in the job control.

NAT0932: Program version error.

Text
Program version error.
Explanation
The executing program has been recataloged by another user
between screen I/Os (that is, it is possible that the program
has been stowed by a second user while a first user is still
using it).
Action
Contact your Natural administrator.

NAT0933: GDA time-stamp conflict.

Text
GDA time-stamp conflict.
Explanation
This error occurs if a program references a global data area (GDA)
which was recataloged or a GDA that has been moved from another
environment after the program has been cataloged. Also the program
that references the GDA could have been moved from a different
environment into the current one causing a GDA time-stamp conflict.
If a GDA is cataloged again, all objects which reference the GDA
must also be cataloged again.
Action
Check the program structure and recatalog if necessary, or use the
the compile option GDASC=ON. On a mainframe platform, you may
consider setting the profile parameter RECAT=ON.

NAT0934: GDA :1: conflicts with active GDA :2:.

Text
GDA ... conflicts with active GDA ....
Explanation
A Natural subprogram, i.e. an object executing at a level > 1, is trying
to overwrite an existing GDA.

An existing GDA can only be overwritten by a main program, i.e. an
object executing at level 1.
Action
Check program and correct error.

NAT0935: Conflicting number of parameters (:1: :2:/:3:/:4:/:5:).

Text
Conflicting number of parameters (:1: :2:/:3:/:4:/:5:).
Explanation
The number of parameters defined in object :2: (of type :1:, loaded
from library :3:, database :4:, file number :5:) does not
correspond to the number of parameters used to invoke the object.
Action
Check program and correct error.

NAT0936: Format/length conflict in parameter :1: (:2: :3:/:4:/:5:/:6:).

Text
Format/length conflict in parameter :1: (: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 the format/length of the corresponding parameter used to
invoke it.
The following conditions must be met:
  - The formats must be equal.
  - The lengths must be equal.
  - The precisions must be equal.
Action
Check program and correct error.

NAT0937: Wrong array defined in param. :1: (:2: :3:/:4:/:5:/:6:).

Text
Wrong array defined in param. :1: (:2: :3:/:4:/:5:/:6:).
Explanation
The array defined as parameter at position :1: in object :3: (of
type :2:, loaded from library :4:, database :5:, file number :6:)
does not match the array or array range used as corresponding parameter
to invoke it.

The following conditions must be met:
  - The ranks must be equal.
  - The occurrences of each dimension must be equal.


This error also occurs if a 3GL routine calls a subprogram, and
the subprogram's PDA specifies a variable array range (1:V).
Action
Check program and correct error.

NAT0938: Prot. param. :1: used as target field (:2: :3:/:4:/:5:/:6:/).

Text
Prot. param. :1: used as target field (: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:) is used
as a target operand. However, this parameter is protected: it is
a constant, or it has the attribute (AD=ON), and must not be modified.
Action
Check program and correct error.

NAT0939: Natural editor is not linked and cannot be loaded.

Text
Natural editor is not linked and cannot be loaded.
Explanation
The Natural editor modules are not linked and cannot be loaded.
Action
Contact your database administrator.

NAT0940: This terminal command is not supported.

Text
This terminal command is not supported.
Explanation
Terminal commands for screen paging cannot be used under
every TP monitor.
Action
Enter a valid command.

NAT0941: Invalid size for screen-paging system file.

Text
Invalid size for screen-paging system file.
Explanation
A screen-paging command was entered, but the size of the
system file used for screen paging was '0', which means
that no screens can be stored.
Action
Restart Natural session with valid size for screen-paging system file.

NAT0942: Invalid use of hardcopy facility.

Text
Invalid use of hardcopy facility.
Explanation
The Natural hardcopy facility is only available under the
TP monitor Com-plete.
Action
Enter a valid Natural command.

NAT0943: Screen paging open function failed.

Text
Screen paging open function failed.
Action
Check the status of the screen-paging system file.

NAT0944: Screen paging record overflow.

Text
Screen paging record overflow.
Explanation
An attempt was made to write to the screen-paging system file
a record which was larger than the screen page size.
Action
Increase the size of the physical terminal buffer.

NAT0946: Screen paging write failed.

Text
Screen paging write failed.
Explanation
An error occurred during an attempt to write a screen to the
screen-paging system file.
Action
Check the status of the screen-paging system file.

NAT0947: Screen paging read failed.

Text
Screen paging read failed.
Explanation
An error occurred during an attempt to read a screen from the
screen-paging system file.
Action
Check the status of the screen-paging system file.

NAT0949: Limit of :1: concurrent sessions exceeded for user :2:.

Text
Limit of ... concurrent sessions exceeded for user ....
Explanation
The maximum number of concurrent sessions allowed for the user
as indicated in the message has been exceeded.
Action
Reduce the number of concurrent sessions.

NAT0950: Abnormal end due to unhandled LE condition :1:.

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.