| Text | Session terminated due to license check failure. |
| Expl. | The session terminated due to a problem with your product
license. Natural cannot start without a valid license. The license module is either not linked or invalid or insufficient for your environment. |
| Actn. | Check the session initialization error messages for more detailed information about the problem. If you have no correct license file, please contact Software AG. |
| Text | Termination forced by unhandled LE condition - .... |
| Expl. | 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. Accordung to the DU profile parameter, Natural has been terminated with a dump. |
| Actn. | 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 | Natural termination forced by DUE - :1: :2: :3:. |
| Expl. | Error :3: has occurred, and Natural has been terminated with a
dump. The Natural program :1: has caused the error on line number :2:. :3: is the error message ID which was defined by profile parameter parameter DUE to get a dump. If :1: and :2: are missing, there wasn"t any program active when the error occurred. |
| Actn. | Analyse the dump which has been produced, and correct the error. If necessary, contact Software AG Support. |
| Text | Natural escaped from error loop - :1: :2: :3:. |
| Expl. | An error :3: loop has occurred, and Natural has been terminated. The Natural program :1: has caused the error on line number :2:. If the parameter DU=FORCE is set, a dump will be produced. Register 1 in the dump contains the number of the last error which occurred before Natural escaped from the error loop and issued NAT9969. |
| Actn. | Correct the error, or produce a dump by setting DU=FORCE. If necessary, contact Software AG Support. |
| Text | Natural initialization failed due to ITERM=ON. |
| Expl. | During the initialization of Natural, an error condition
occurred. This message is preceded by one or more other Natural error messages. The session is terminated because profile parameter ITERM=ON is set. |
| Actn. | Correct the error as indicated by the preceding error messages, or set ITERM=OFF (not possible with STACK=INPL). |
| Text | Session terminated by front-end driver - RC=:1:. |
| Expl. | During session initialization, the environment- dependent driver has detected a crucial error and the session cannot be continued. RC=:1: indicates the driver-error reason code. |
| Actn. | Contact Software AG Support. |
| Text | Natural module missing or invalid - :1:. |
| Expl. | During initialization Natural has detected that the module :1: is missing or its maintenance level does not match. |
| Actn. | Link the correct module to the Natural nucleus and restart
Natural. |
| Text | Abend :1: :2:. |
| Expl. | An unexpected internal runtime error has occurred. The session
was terminated and a dump was produced. :1: is name of the nucleus component which caused the error. :2: contains additional error information (optional). |
| Actn. | Save the dump and contact Software AG Support. |
| Text | Natural termination forced by abend .... |
| Expl. | Natural has been abnormally terminated after the abend condition shown in the error message has occurred, and the profile parameter DU=ON was set. The abend condition was set by the operating system and/or TP system in use. For an explanation of the abend condition, see the appropriate operating-system or TP-system documentation. Possible abend conditions are, for example: "S0C7" - data exception, "AICA" - possible loop under CICS, "ATCH" - task cancelled by operator (CICS). |
| Actn. | Analyse the dump which has been produced, and correct the error. If necessary, contact Software AG Support. |
| Text | Back-end program not found - :1:. |
| Expl. | The Natural session was terminated normally, but the program :1:, which should receive control after the session termination (as specified with the profile parameter PROGRAM), could not be found. |
| Actn. | Make sure that the correct program name is specified with the
PROGRAM parameter and the program is contained in the appropriate library. |
| Text | Initialization buffer too small. |
| Expl. | Natural could not be initialized because there was not enough
space in the initialization buffer. The size of this buffer is determined by the profile parameter ISIZE. |
| Actn. | Increase value for ISIZE parameter in the Natural parameter
module, then start Natural session again. |
| Text | Permanent I/O error during input processing. |
| Expl. | During batch processing, Natural did not receive any input data. Or: During online processing, this message is issued to the console in case of an I/O error, because in such a case the associated output device is considered to be inoperational. |
| Actn. | Make sure input data are passed correctly to Natural. |
| Text | Error occurred during execution/compilation. |
| Expl. | During Natural batch processing, an error has occurred when a
program was being compiled or executed. Batch processing was continued after the error. The session was terminated with return code "4". |
| Actn. | Check the output protocol for any error messages. Correct the error, and re-run the batch job if necessary |
| Text | Terminal converter module not linked - ... |
| Expl. | Natural was invoked with terminal type ... which cannot be
supported because the corresponding converter module for this terminal type has not been linked to the Natural nucleus or is incompatible with the current environment. |
| Actn. | Link the missing module to the Natural nucleus or specify a
correct terminal type by means of the profile parameter TTYPE. |
| Text | Nucleus module does not reside in residentpage - .... |
| Expl. | The called program is not loaded as a Com-plete resident program. |
| Actn. | Load the program as a Com-plete resident program. |
| Text | GETMAIN for back-end program data failed. |
| Expl. | The size requested for the back-end program data cannot be
allocated in the Natural thread. |
| Actn. | Increase the thread size. |
| Text | Error occurred during session termination. |
| Expl. | An error has occurred during session termination. The corresponding error message has been issued before. |
| Actn. | Check the corresponding error message and correct the error if necessary. |
| Text | Conversation I/O requested, nucleus/thread displaced. |
| Expl. | The nucleus and/or the thread has been displaced during the last terminal I/O. |
| Actn. | Place the Natural nucleus in the (E)LPA and/or do not specify RELO=FORCE/ON. |
| Text | Natural address relocation failed - RC=.... |
| Expl. | An internal error has occurred. |
| Actn. | Contact Software AG support. |
| Text | Thread-locked sessions cannot be recovered. |
| Expl. | Com-Plete tries to recover a Natural session, which is not
possible as the session runs in RELO=OFF mode. The session must be terminated. |
| Actn. | Restart session with RELO=ON. |
| Text | Natural parameter module missing or invalid. |
| Expl. | Either no Natural parameter module has been linked to the Natural nucleus, or the parameter module linked contains an error. |
| Actn. | Re-assemble Natural parameter module using the correct macro
library, and link it to the Natural nucleus. |
| Text | Natural session terminated abnormally - RC=:1:. |
| Expl. | The Natural session was terminated by a TERMINATE statement with return code :1: in a Natural program. |
| Actn. | No action required. |
| Text | Invalid system file information. |
| Expl. | The database ID and/or file number of the Natural system file
FNAT have been changed, but the Natural system environment has not been adjusted to this change. |
| Actn. | Use function "A" of the INPL utility to adjust the
system environment. |
| Text | Natural versions do not agree. |
| Expl. | During initialization, Natural checks whether the versions of the environment-dependent interface, the Natural nucleus and the Natural parameter module fit together. |
| Actn. | Re-assemble the parameter module and/or the interface, and
re-link the Natural nucleus. |
| Text | Natural initialization failed. |
| Expl. | During initialization of Natural, an error condition occurred
which does not allow for continuation of the Natural session. This message is preceded by one or more other Natural error messages. |
| Actn. | Correct error as indicated by preceding error messages. |
| Text | Required module not linked - :1:. |
| Expl. | During initialization Natural has detected that module :1: is
missing. The module is required to run the Natural nucleus. |
| Actn. | Link the missing module to the Natural nucleus and restart
Natural. |
| Text | Session terminated due to unrecoverable abend :1:. |
| Expl. | During the attempt to recover the Natural session from abend :1:, another abend has occurred. To avoid an abend loop, the Natural session was terminated. |
| Actn. | Analyse the dump which has been produced, and correct the error. If necessary, contact Software AG Support. |
| Text | Adabas link module missing or invalid - :1:. |
| Expl. | The Adabas link module :1: specified by profile parameter ADANAME cannot be loaded or is invalid. Either the load library is missing or invalid, or the specified module does not exist or has been linked incorrectly. |
| Actn. | Ensure that the correct load library is attached to the Natural session and that it contains the correct Adabas link module. |
| Text | Dynamic parameter string is too long. |
| Expl. | The character string supplied as dynamic parameters at the start
of the Natural session is too long. It must not exceed 32767 characters. This includes the dynamic parameters read from the CMPRMIN file. |
| Actn. | Restart the Natural session with fewer dynamic parameters. |
| Text | Natural session terminated normally. |
| Expl. | The Natural session for this terminal/user was terminated without any error conditions. Natural was terminated by one of the following actions: - entering the command FIN in NEXT/MORE mode, - entering the command %% in NEXT mode, - pressing the CLEAR key in NEXT mode, - executing the statement TERMINATE in a Natural program. |
| Actn. | No action required. |
| Text | Unable to load Natural nucleus module - :1: :2:. |
| Expl. | Natural could not load its shared or reentrant nucleus module
:1:. The front-end part of Natural attempted a TP- or OS-dependent load request and received error condition :2:. |
| Actn. | Check the shared nucleus name specified by the NUCNAME parameter
or re-link the reentrant part with a corresponding name. Check whether the correct load library is accessible by Natural. |
| Text | Not enough memory to start Natural - :1: :2:K RC=:3:. |
| Expl. | Natural was not able to acquire all required storage buffers. These buffers are used for user area, terminal area, I/O areas, file buffers, etc. If one of the storage acquisition calls fails, Natural cannot be initialized. Additional information as follows: :1: buffer type (as documented in NATCONFG), :2: buffer size (in KB), :3: return code from the GETMAIN request: 04 = Not enough storage. 08 = Invalid buffer type. 10 = Duplicate buffer type. 18 = Invalid buffer length. 1C = Buffer type not defined in NATCONFG. 30 = Module NATCONFG not linked. 34 = Physical GETMAIN failed. |
| Actn. | 34 = Physical GETMAIN failed. RC=04/34: Reduce buffer sizes or
assign a larger thread/partition. The other return codes indicate a product error; contact Software AG support. |
| Text | I/O error on input file - :1:. |
| Expl. | An I/O error occurred during batch processing on an input file, e.g. CMSYNIN or CMOBJIN. :1: indicates the name of the input file. |
| Actn. | Check for operating-system error messages in the job log and
correct the error. |
| Text | I/O error on output file - :1:. |
| Expl. | An I/O error occurred during batch processing on an output file, e.g. CMPRINT. :1: indicates the name of the output file. |
| Actn. | Check for operating-system error messages in the job log and
correct the error. |
