Natural System Error Messages 9901-9950

NAT9901: Natural/TSO runtime environment is not TSO.

Text
Natural/TSO runtime environment is not TSO.
Explanation
Natural/TSO has been started in a non-TSO environment.
Action
Natural/TSO can run in a TSO environment only. Link the appropriate
frontend interface for this environment to your nucleus.

NAT9902: Dataset cannot be opened - :1:.

Text
Dataset cannot be opened - ....
Explanation
The required dataset cannot be opened. Either it is not or
incorrectly defined in the JCL, or it cannot be opened due to other
reasons.
Action
Supply the correct dataset definition in the JCL. Check for
operating-system error messages in the job log to ascertain the cause
of the error.

NAT9903: NATSTUB not linked to Natural nucleus :1:.

Text
NATSTUB not linked to Natural nucleus :1:.
Explanation
Either the module NATSTUB is not linked to the Natural nucleus; or
the shared nucleus :1: has been loaded; but NATSTUB is not defined
as its entry point.
Action
Link the module NATSTUB to the Natural nucleus. If a shared nucleus
is used, specify CMSTUB as its entry point in the link job.

NAT9904: Invalid Natural nucleus - :1:.

Text
Invalid Natural nucleus - ....
Explanation
The version of the Natural nucleus module, as indicated in the error
message, does not correspond to the front-end interface module.
For example, the front-end has loaded a shared nucleus of a different
version.
Action
Link the correct Natural nucleus; or specify a correct shared nucleus
name, using the profile parameter NUCNAME.

NAT9905: Terminal I/O error - :1:: RC=:2:.

Text
Terminal I/O error - :1:: RC=:2:.
Explanation
A terminal I/O error has occurred. The I/O response code RC=:2:
indicates the reason for the failure of request :1:.
Under TSO, the response code comes from the failing TSO I/O request
macro TPUT or TGET.
Action
Check the meaning of the response code in the TSO documentation.
Contact Software AG Support for further problem analysis.

NAT9906: Natural server cannot run as LE main routine.

Text
Natural server cannot run as LE main routine.
Explanation
The Natural front-end (NATOS) received control from a front-end server
stub which did not initialize the IBM language environment. NATOS is
linked with LE support and cannot run as an LE main routine.
Action
Either link NATOS without LE support or generate the front-end server
stub with LE support if possible.

NAT9907: Unsupported operating-system version.

Text
Unsupported operating-system version.
Explanation
The current operating-system version is not supported by this
Natural version.
Action
See Natural documentation for supported operating systems and versions.

NAT9908: Nucleus module does not reside below 16 MB line - :1:

Text
Nucleus module does not reside below 16 MB line - ...
Explanation
The nucleus module specified in the message must be executed
below the 16 MB line due to operating-system requirements.
Action
Re-link the specified nucleus module with parameter MODE RMODE(24).

NAT9909: Unsupported teleprocessing system version.

Text
Unsupported teleprocessing system version.
Explanation
This version of the teleprocessing system (e.g. Com-plete) is not
supported by Natural. It is either an old version which does not
contain the facilities required by Natural, or a new version which is
not yet supported by your version of Natural.
Action
Either install a newer version of the teleprocessing system,
or install a newer version of Natural.

NAT9910: Session communication area missing or invalid.

Text
Session communication area missing or invalid.
Explanation
The Natural server session communication area is missing or invalid.
The session communication area is internally used by the Natural
server and must be supplied by the front-end server stub.
Action
Contact Software AG Support for further problem analysis.

NAT9911: Invalid storage thread size specified.

Text
Invalid storage thread size specified.
Explanation
Running Natural as a server requires the acquisition of main-storage
threads of a fixed size. The thread size defined by the front-end
server stub is invalid. It must be in the range from 256 kilobytes
to 16 megabytes.
Action
Specify a correct thread size in the front-end server stub definitions.

NAT9912: The number of threads is invalid or too high.

Text
The number of threads is invalid or too high.
Explanation
Running Natural as a server requires the acquisition of main-storage
threads. The number of threads defined by the front-end server stub
is invalid or too great. It must be in the range from 0 to 8191, and
the total thread storage must be less than 2 gigabytes.
Action
Reduce the number of threads or the thread size in the front-end
server stub definitions.

NAT9913: Server environment already initialized.

Text
Server environment already initialized.
Explanation
The front-end server stub requested Natural to initialize the server
environment, but the server environment has already been initialized.
Action
Terminate the server environment before restarting it.
Contact Software AG Support for further problem analysis.

NAT9914: GETMAIN for common server table failed.

Text
GETMAIN for common server table failed.
Explanation
The Natural server environment cannot be initialized because the
GETMAIN for its central control block has failed. Sufficient region
storage must be available.
Action
Increase the region size for the Natural server. If the problem cannot
be solved, contact SAG technical support for further problem analysis.

NAT9915: GETMAIN for thread storage failed.

Text
GETMAIN for thread storage failed.
Explanation
The Natural server environment cannot be initialized because a
GETMAIN for its storage threads has failed. Sufficient region
storage must be available.
Action
Increase the region size for the Natural server or reduce the number
or the size of its storage threads in the frontend stub definitions.

NAT9916: Error retrieving server name token. RC=:1:.

Text
Error retrieving server name token. RC=....
Explanation
The central anchor for the Natural server is an MVS name token.
The retrieve request for the name token has failed with the decimal
return code shown in the message. The explanation of the return code
can be found in the IBM MVS Authorized Assembler Services Reference
under the IEANTRT macro call description.
Action
If you cannot find the reason for the problem and correct it, contact
Software AG technical support for further problem analysis.

NAT9917: Error creating server name token. RC=:1:.

Text
Error creating server name token. RC=....
Explanation
The central anchor for the Natural server is an MVS name token.
The create request for the name token has failed with the decimal
return code shown in the message. The explanation of the return code
can be found in the IBM MVS Authorized Assembler Services Reference
under the IEANTCR macro call description.
Action
If you cannot find the reason for the problem and correct it, contact
Software AG technical support for further problem analysis.

NAT9918: Error deleting server name token. RC=:1:.

Text
Error deleting server name token. RC=....
Explanation
The central anchor for the Natural server is an MVS name token.
The delete request for the name token has failed with the decimal
return code shown in the message. The explanation of the return code
can be found in the IBM MVS Authorized Assembler Services Reference
under the IEANTDL macro call description.
Action
If you cannot find the reason for the problem and correct it, contact
Software AG technical support for further problem analysis.

NAT9919: Invalid server function code.

Text
Invalid server function code.
Explanation
The frontend server stub called the Natural server with an
invalid server function code.
Action
Contact SAG technical support for further problem analysis.

NAT9920: Roll server not active. SUBSID=:1:.

Text
Roll server not active. SUBSID=:1:.
Explanation
The Natural server environment requires the Natural roll server for
running multiple server sessions within a limited number of storage
threads. Either there is no roll server started for the specified
Natural subsystem ID or the SUBSID profile parameter is incorrectly
or dynamically specified in the Natural parameter module.
Action
Start the Natural roll server for the subsystem ID or set the SUBSID
profile parameter correctly or use SUBSID=' ' to run without a roll
server or specify this in the frontend server stub definitions.

NAT9921: Server environment not initialized.

Text
Server environment not initialized.
Explanation
The frontend server stub called Natural with a server function
code other than 'initialize server' and the Natural server
environment is in uninitialized state.
Action
Restart the frontend server stub to reset its state completely.
Contact SAG technical support for further problem analysis.

NAT9922: The initialization session cannot be rolled.

Text
The initialization session cannot be rolled.
Explanation
The frontend server stub requested a session create, roll-out
or roll-in server function while the Natural server was initializing.
During the server initialization phase these server functions are
not allowed.
Action
Contact SAG technical support for further problem analysis.

NAT9923: No server clone session available.

Text
No server clone session available.
Explanation
The frontend server stub requested a session create but the
clone session had not been saved yet.
Action
Contact SAG technical support for further problem analysis.

NAT9924: Session ID missing or invalid.

Text
Session ID missing or invalid.
Explanation
The Natural server session ID is a unique internal ID to identify
a Natural session. The frontend server stub passed either no
session ID or a hexadecimal null session ID which is not allowed
or the session ID hads been modified.
Action
Contact SAG technical support for further problem analysis.

NAT9925: Session ID already exists.

Text
Session ID already exists.
Explanation
The front-end server stub requested a 'session create' but a
session with the same session ID exists already and
is ready to run.
Action
Contact Software AG Support for further problem analysis.

NAT9926: Session not in rolled-in status.

Text
Session not in rolled-in status.
Explanation
The frontend server stub requested a session roll-out, execute
or save clone function, but the session is not in rolled-in state.
Action
Contact SAG technical support for further problem analysis.

NAT9927: Session not in rolled-out status.

Text
Session not in rolled-out status.
Explanation
The frontend server stub requested a session roll-in function,
but the session is not in rolled-out state.
Action
Contact SAG technical support for further problem analysis.

NAT9928: Compression failed during roll-out. RC=:1:.

Text
Compression failed during roll-out. RC=....
Explanation
The Natural thread storage compression failed. The exact reason
is indicated by the decimal return code RC=00nn. It is explained in
the Natural documentation.
Action
Contact Software AG support for further problem analysis.

NAT9929: Decompression failed during roll-in. RC=:1:.

Text
Decompression failed during roll-in. RC=....
Explanation
The Natural thread storage decompression failed. The exact reason
is indicated by the decimal return code RC=00nn. It is explained in
the Natural documentation.
Action
Contact SAG technical support for further problem analysis.

NAT9930: GETMAIN failed for roll buffer.

Text
GETMAIN failed for roll buffer.
Explanation
During Natural session thread storage roll-out the GETMAIN request
for the roll buffer failed. Sufficient region storage must be
available to save the compressed session storage.
Action
Increase the region size for the Natural server or use the Natural
roll server as roll facility.

NAT9931: The AUTOTERM facility cannot be initialized.

Text
The AUTOTERM facility cannot be initialized.
Explanation
In a Natural server environment, the automatic server termination
facility helps to avoid problems caused by an unintended DETACH of
the server initialization TCB (e.g. MVS abends A03, no server resource
cleanup etc.). The AUTOTERM facility cannot be initialized due to
storage protection problems.
Action
Disable the AUTOTERM facility in the frontend server stub definitions
or contact SAG technical support for further problem analysis.

NAT9932: Natural runtime error occurred - :1:.

Text
Natural runtime error occurred - :1:.
Explanation
During the execution of a Natural server session, the indicated
Natural runtime error :1: occurred.
Action
Check the complete runtime error message issued by Natural.
It can be found either in the return data on the client side
or in the Natural standard output dataset of the server.

NAT9933: Roll server ALLOCATE request failed. RC=:1:/:2:.

Text
Roll server ALLOCATE request failed. RC=.../....
Explanation
During session creation, the ALLOCATE request for a new roll-file slot
failed. Sufficient roll-file storage must be available. The reason
for the failure is indicated by the decimal return/reason codes. These
are explained in the Natural documentation.
Action
If you cannot find the reason for the problem and correct it, contact
Software AG support for further problem analysis.

NAT9934: Roll server WRITE request failed. RC=:1:/:2:.

Text
Roll server WRITE request failed. RC=.../....
Explanation
During session roll-out, the WRITE request to the Natural roll server
failed. The reason for the failure is indicated by the decimal
return/reason codes. These are explained in the Natural documentation.
Action
If you cannot find the reason for the problem and correct it, contact
Software AG support for further problem analysis.

NAT9935: Roll server READ request failed. RC=:1:/:2:.

Text
Roll server READ request failed. RC=:1:/:2:.
Explanation
During session roll-in the READ request from the Natural roll server
failed. The reason for the failure is indicated by the decimal
return/reason codes. These are explained in the Natural Documentation.
Action
If you cannot find the reason for the problem and correct it, contact
SAG technical support for further problem analysis.

NAT9936: Roll server FREE request failed. RC=:1:/:2:.

Text
Roll server FREE request failed. RC=.../....
Explanation
During session termination, the FREE request to the Natural roll
server failed. The reason for the failure is indicated by the
decimal return/reason codes. These are explained in the Natural
documentation.
Action
If you cannot find the reason for the problem and correct it, contact
Software AG support for further problem analysis.

NAT9937: Server I/O subtask cannot be started. RC=:1:/:2:.

Text
Server I/O subtask cannot be started. RC=:1:/:2:.
Explanation
In the Natural server environment, the whole I/O handling is done
by a separate MVS subtask, started during server initialization.
The ATTACH request for the I/O subtask failed. The reason for the
failure is indicated by RC=:1:/:2:, where :1: is the decimal return
code of the internal function code :2:.
Action
Contact Software AG Support for further problem analysis.

NAT9938: Termination of SMARTS environment failed.

Text
Termination of SMARTS environment failed.
Explanation
No further explanation available.
Action
Contact Software AG support.

NAT9939: :1: RC=:2:

Text
Remote front-end communication error. RC=...
Explanation
A Natural server environment uses the Natural remote front-end to
dispatch a Natural session in a remote TP environment. This is used,
for example, by the CICS or IMS Adapter for NDV or NWO.
This error indicates an error in the communication between the
Natural server environment and the remote TP environment.
The meaning of the RC value depends on the error text. For example:
- 'Cannot load NCI front-end RC= ':
  RC contains the CICS EIB response code.
- 'Error at Remote Gateway Obtain/Restore':
  RC contains the response code from the NDV remote gateway.
Action
In case of a CICS EIB response code, examine the CICS messages or the
remote front-end trace for further error information.
In case of a remote gateway RC, contact Software AG technical support.

NAT9940: Server parameter list(s) missing or invalid.

Text
Server parameter list(s) missing or invalid.
Explanation
A mandatory Natural server parameter list is missing or invalid.
A Natural front-end server stub communicates with a Natural server
session using internal parameter lists, which are mandatory
depending on the internal server function.
Action
Contact Software AG Support for further problem analysis.

NAT9941: Wrong Smarts version for use of LE/370.

Text
Wrong Smarts version for use of LE/370.
Explanation
Smarts version V272 is required to support the CEEPIPI interface for
LE/370 programs.
Action
Install the required Smarts version.

NAT9942: Server Front-End incompatible with Natural version.

Text
Server Front-End incompatible with Natural version.
Explanation
The Front-End Server Stub requires a Natural version different from
the version of the current Natural environment-dependent nucleus.
Action
Install and use a compatible Natural version according to the
Front-End Server Stub documentation.

NAT9943: Logic error in Natural program for asynchronous session.

Text
Logic error in Natural program for asynchronous session.
Explanation
Input data requested, but an asynchronous session runs without any
input device.
To avoid this error situation, check the Natural system variable
*SCREEN-IO.
Action
Correct the program logic.