Natural System Error Messages 6250-6299

#### Search Results

Search

# Natural System Error Messages 6250-6299

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

#### NAT6251: Unknown OPD format found during dynamic operand processing

    Text
    Unknown OPD format found during dynamic operand processing
    Explanation
    Internal Error.
    An unknown Natural internal operand format was found during the
    processing of a dynamic variable.
    Action
    Contact the technical support.

#### NAT6252: Resize of a non dynamic variable not possible

    Text
    Resize of a non dynamic variable not possible
    Explanation
    Internal Error.
    An invalid Natural internal operand format was found, when the
    value space for a dynamic variable was resized.
    Action
    Contact the technical support.

#### NAT6253: Upper limit for dynamic variable exceeded

    Text
    Upper limit for dynamic variable exceeded
    Explanation
    During the reallocation of the value space of a dynamic variable,
    the upper limit of 1 GB was exceeded.
    Action
    Ensure that the data space of a dynamic variable stays below 1 GB.

#### NAT6254: Invalid size value for REDUCE or EXPAND statement specified: :1:

    Text
    Invalid size value for REDUCE or EXPAND statement specified:<size value>
    Explanation
    A size value is specified with the REDUCE and the EXPAND statements,
    in order to reallocate the memory for the given dynamic operand.
    The following conditions must be kept for the size value:
    1. The size value must not be negative
    2. The size value must not exceed 1 Gigabyte
    Action
    The size value, which leads to the error, is displayed in the error
    message. Check the value against the conditions mentioned above.

#### NAT6255: Invalid usage of dynamic variable with *length = 0

    Text
    Invalid usage of dynamic variable with *length = 0
    Explanation
    An dynamic variable may have no data assigned, which means, the data
    length is 0. The content of the dynamic variable is then undefined.
    The usage of a dynamic variable without data leads to an error, when
    the following conditions are given:
    1. The dynamic variable is used as operand in a logical condition
       criteria
    2. The dynamic variable is used as source operand in an assignment.
    Action
    Check the usage of the dynamic variable and ensure, that there is data
    assigned to it.

#### NAT6256: X-arrays cannot be specified in this context.

    Text
    X-arrays cannot be specified in this context.
    Explanation
    The specification of X-arrays is not allowed in this context.
    Action
    Check program and correct error.

#### NAT6269: Natural application terminated abnormally.

    Text
    Natural application terminated abnormally.
    Explanation
    The Natural application was terminated abruptly due to a hardware or
    software exception (e.g., memory access violation or stack overflow).
    Action
    If you are running Natural interactively, it is recommended that you
    save any changes and restart Natural as soon as possible.
    For a resolution of the problem, please contact technical support.

#### NAT6270: Natural Debugger could not be loaded.

    Text
    Natural Debugger could not be loaded.
    Explanation
    Insufficient memory or incorrect PATH setting.
    Action
    Check that the PATH environment variable contains the path
    to the directory where the Natural Debugger is located and
    check that you have enough memory to load the Natural Debugger.

#### NAT6271: Internal error while creating debugger communication.

    Text
    Internal error while creating debugger communication.
    Explanation
    Internal error.
    Action
    Contact technical support.

#### NAT6272: Event not allowed.

    Text
    Event not allowed.
    Explanation
    You specified an event which is allowed only internally (e.g.,
    OPEN, AFTER-OPEN).
    Action
    Correct the error by using a different event name.

#### NAT6273: AIV/GP version compatibility error

    Text
    AIV/GP version compatibility error
    Explanation
    The current application uses new and old catalogued Natural objects.
    A new object has created an AIV which starts beyond 64kB. An old
    Natural object tries to access this AIV, but is limited to the 64kB
    size.
    Action
    You have two possibilities:
    a) Recatalog the object (preferred).
    b) Rearrange AIV creation.

#### NAT6274: Parameter :1: is too long for this interface

    Text
    Parameter ... is too long for this interface
    Explanation
    The traditional form of the Natural CALL statement supports only lengths
    up to 65535. This length can be exceeded by LARGE and DYNAMIC variables.
    Use the INTERFACE4 option for the CALL statement and write a new user
    exit to use the new interface. Use a new name for the user exit so that
    a call to the old user exit with traditional syntax doesn"t crash.
    Action
    If this error occurs for a different statement, call technical support.

#### NAT6275: The type of parameter :1: is illegal for this interface

    Text
    The type of parameter ... is illegal for this interface
    Explanation
    The statement CALL INTERFACE4 does not allow operands of type HANDLE.
    Action
    Remove the operands of type HANDLE from the CALL statement.

#### NAT6276: Info: :1:.

    Text
    Info: :1:.
    Explanation
    Additional information concerning the following error message is
    displayed.

#### NAT6296: Fatal error in the communication.

    Text
    Fatal error in the communication.
    Explanation
    Either the communication with the Entire Screen Builder or Web I/O
    Interface client was interrupted, or a Natural nucleus was started which
    is not meant to be started from a Unix terminal (e.g. Natural
    nucleus for Entire Screen Builder was used or the profile parameter
    WEBIO is ON).
    Action
    Either reconnect, or use a Natural nucleus which is intended for
    starting from a Unix terminal.