Natural System Error Messages 9950-9999

#### Search Results

Search

# Natural System Error Messages 9950-9999

#### NAT9963: Pre-initialized thread cannot be used - :1: :2:.

    Text
    Pre-initialized thread cannot be used - :1: :2:.
    Explanation
    The pre-initialized thread defined by profile parameter THPINIT has
    been accessed. It cannot be used because one of the prerequisites
    isn"t fulfilled or any other error has occurred.
    :1: Name of pre-initialized thread storage (profile parameter THPINIT)
    :2: Character string and reason code indicating the error cause:
        NOTHREAD     - this is no thread environment
        NOSPACE      - not enough working storage available
        SCRNSIZE     - the current session has a different screen size
        DECOMP  .... - thread decompression error X"...." occurred
        ROLLIN  .... - thread roll-in error number X"...." has occurred
    Action
    Correct the error and restart the session. You can bypass the usage of
    a pre-initialized thread by specifying profile parameter THPINIT=" ".

#### NAT9964: NAT9964 Error occurred during session initialization.

    Text
    NAT9964 Error occurred during session initialization.
    Explanation
    During the initialization of Natural batch processing, an error has
    occurred. Batch processing has continued after the error, because
    parameter ITERM=OFF was set. The session terminates with return
    code "4".
    Action
    Correct the error as indicated by the preceding error messages.

#### NAT9965: Natural termination forced by administrator - :1:.

    Text
    Natural termination forced by administrator - ....
    Explanation
    The session has been marked for termination by the Review for Natural
    command TERMNAT within the Review SYSRNM administrator application.
    When the session resumes after a terminal I/O, it is terminated.
    The user ID ... of the Review SYSRNM administrator is indicated
    at the end of the message.
    Action
    None.

#### NAT9966: Session terminated due to license check failure.

    Text
    Session terminated due to license check failure.
    Explanation
    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.
    Action
    Check the session initialization error messages for more detailed
    information about the problem. If you have no correct license
    file, please contact technical support.

#### NAT9967: Termination forced by unhandled LE condition - :1:.

    Text
    Termination forced by 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.
    Accordung to the DU profile parameter, Natural has been terminated
    with a dump.
    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.

#### NAT9968: Natural termination forced by DUE - :1: :2: :3:.

    Text
    Natural termination forced by DUE - :1: :2: :3:.
    Explanation
    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.
    Action
    Analyse the dump which has been produced, and correct the error.
    If necessary, contact technical support.

#### NAT9969: Natural escaped from error loop - :1: :2: :3:.

    Text
    Natural escaped from error loop - prog line NATnnnn.
    Explanation
    An error loop has occurred, and Natural has been terminated.
     prog    - is the name of the program which caused the error.
     line    - is the number of the source-code line which caused the error.
     NATnnnn - is the number of the last error which occurred before
                  NAT9969 was issued.
    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.
    Action
    Correct error, or produce a dump by setting DU=FORCE.
    If necessary, contact technical support.

#### NAT9970: Natural initialization failed due to ITERM=ON.

    Text
    Natural initialization failed due to ITERM=ON.
    Explanation
    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.
    Action
    Correct the error as indicated by the preceding error messages,
    or set ITERM=OFF (not possible with STACK=INPL).

#### NAT9971: Session terminated by front-end driver - RC=:1:.

    Text
    Session terminated by front-end driver - RC=:1:.
    Explanation
    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.
    Action
    Contact technical support.

#### NAT9972: Natural module missing or invalid - :1:.

    Text
    Natural module missing or invalid - :1:.
    Explanation
    During initialization Natural has detected that the module :1:
    is missing or its maintenance level does not match.
    Action
    Link the correct module to the Natural nucleus and restart Natural.

#### NAT9973: Abend :1: :2:.

    Text
    Abend :1: :2:.
    Explanation
    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).
    Action
    Save the dump and contact technical support.

#### NAT9974: Natural termination forced by abend :1:.

    Text
    Natural termination forced by abend ....
    Explanation
    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).
    If the abend occurred during Adabas call processing, the indicator
    ADABAS is added after the abend code.
    Action
    Analyse the dump which has been produced, and correct the error.
    If necessary, contact technical support.

#### NAT9975: Back-end program not found - :1:.

    Text
    Back-end program not found - :1:.
    Explanation
    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.
    Action
    Make sure that the correct program name is specified with the PROGRAM
    parameter and the program is contained in the appropriate library.

#### NAT9976: Initialization buffer too small.

    Text
    Initialization buffer too small.
    Explanation
    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.
    Action
    Increase value for ISIZE parameter in the Natural parameter module,
    then start Natural session again.

#### NAT9977: Permanent I/O error during input processing.

    Text
    Permanent I/O error during input processing.
    Explanation
    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.
    Action
    Make sure input data are passed correctly to Natural.

#### NAT9978: Error occurred during execution/compilation.

    Text
    Error occurred during execution/compilation.
    Explanation
    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".
    Action
    Check the output protocol for any error messages.
    Correct the error, and re-run the batch job if necessary

#### NAT9979: Terminal converter module not linked - :1:

    Text
    Terminal converter module not linked - ...
    Explanation
    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.
    Action
    Link the missing module to the Natural nucleus or specify a correct
    terminal type by means of the profile parameter TTYPE.

#### NAT9980: Nucleus module does not reside in residentpage - :1:.

    Text
    Nucleus module does not reside in residentpage - ....
    Explanation
    The called program is not loaded as a Com-plete resident program.
    Action
    Load the program as a Com-plete resident program.

#### NAT9981: GETMAIN for back-end program data failed.

    Text
    GETMAIN for back-end program data failed.
    Explanation
    The size requested for the back-end program data cannot be allocated
    in the Natural thread.
    Action
    Increase the thread size.

#### NAT9982: Error occurred during session termination.

    Text
    Error occurred during session termination.
    Explanation
    An error has occurred during session termination.
    The corresponding error message has been issued before.
    Action
    Check the corresponding error message and correct the error
    if necessary.

#### NAT9983: Conversation I/O requested, nucleus/thread displaced.

    Text
    Conversation I/O requested, nucleus/thread displaced.
    Explanation
    The nucleus and/or the thread has been displaced during the last
    terminal I/O.
    Action
    Place the Natural nucleus in the (E)LPA and/or do not specify
    RELO=FORCE/ON.

#### NAT9984: Natural address relocation failed - RC=:1:.

    Text
    Natural address relocation failed - RC=....
    Explanation
    An internal error has occurred.
    Action
    Contact technical support.

#### NAT9985: Thread-locked sessions cannot be recovered.

    Text
    Thread-locked sessions cannot be recovered.
    Explanation
    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.
    Action
    Restart session with RELO=ON.

#### NAT9986: Natural parameter module missing or invalid.

    Text
    Natural parameter module missing or invalid.
    Explanation
    Either no Natural parameter module has been linked to the Natural
    environment dependant nucleus, or the parameter module is invalid,
    e.g. it was assembled against a Natural macro library of an older
    version or an older maintenance level.
    Action
    Re-assemble the Natural parameter module using the macro library of
    the current maintenance level and link it to the Natural nucleus.

#### NAT9987: Natural session terminated abnormally - RC=:1:.

    Text
    Natural session terminated abnormally - RC=:1:.
    Explanation
    The Natural session was terminated by a TERMINATE statement with
    return code :1: in a Natural program.
    Action
    No action required.

#### NAT9988: Error in system file access.

    Text
    Error in system file access.
    Explanation
    When a new session starts up, Natural submits various database calls to
    check the reachability and integrity of the FNAT System File. If any of
    these database calls receives a response code or if the specified FNAT
    system file can not be identified as valid, the initialization process
    is stopped and the session terminates.
    In addition to this message, another message is displayed before,
    giving a more detailed description of the error reason.
    Action
    Check detailed error message, received in addition to this message.

#### NAT9989: Natural versions do not agree.

    Text
    Natural versions do not agree.
    Explanation
    During initialization, Natural checks whether the versions of the
    environment-dependent interface and the Natural shared nucleus
    are of the same Natural major and minor version.
    Action
    Re-assemble and re-link the environment-dependent interface with
    the correct Natural macro and link libraries.

#### NAT9990: Natural initialization failed.

    Text
    Natural initialization failed.
    Explanation
    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.
    Action
    Correct error as indicated by preceding error messages.

#### NAT9991: Required module not linked - :1:.

    Text
    Required module not linked - :1:.
    Explanation
    During initialization Natural has detected that module :1: is missing.
    The module is required to run the Natural nucleus.
    Action
    Link the missing module to the Natural nucleus and restart Natural.

#### NAT9992: Session terminated due to unrecoverable abend :1:.

    Text
    Session terminated due to unrecoverable abend :1:.
    Explanation
    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.
    Action
    Analyse the dump which has been produced, and correct the error.
    If necessary, contact technical support.

#### NAT9993: Adabas link module missing or invalid - :1:.

    Text
    Adabas link module missing or invalid - :1:.
    Explanation
    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.
    Action
    Ensure that the correct load library is attached to the Natural
    session and that it contains the correct Adabas link module.

#### NAT9994: Dynamic parameter string is too long.

    Text
    Dynamic parameter string is too long.
    Explanation
    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.
    Action
    Restart the Natural session with fewer dynamic parameters.

#### NAT9995: Natural session terminated normally.

    Text
    Natural session terminated normally.
    Explanation
    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.
    Action
    No action required.

#### NAT9996: Unable to load Natural nucleus module - :1: :2:.

    Text
    Unable to load Natural nucleus module - :1: :2:.
    Explanation
    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:.
    Action
    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.

#### NAT9997: Not enough memory to start Natural - :1: :2:K RC=:3:.

    Text
    Not enough memory to start Natural - :1: :2:K RC=:3:.
    Explanation
    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.
    Action
    RC=04/34: Reduce buffer sizes or assign a larger thread/partition.
    The other return codes indicate a product error; contact technical
    support.

#### NAT9998: I/O error on input file - :1:.

    Text
    I/O error on input file - :1:.
    Explanation
    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.
    Action
    Check for operating-system error messages in the job log and correct
    the error.

#### NAT9999: I/O error on output file - :1:.

    Text
    I/O error on output file - :1:.
    Explanation
    An I/O error occurred during batch processing on an output file,
    e.g. CMPRINT. :1: indicates the name of the output file.
    Action
    Check for operating-system error messages in the job log and correct
    the error.