Natural System Error Messages 6000-6049

#### Search Results

Search

# Natural System Error Messages 6000-6049

#### NAT6001: Internal error.

    Text
    Internal error.
    Explanation
    Error in internal routine which converts the format of fields.
    Action
    Contact technical support.

#### NAT6003: Incompatible format types used for conversion.

    Text
    Incompatible format types used for conversion.
    Explanation
    An attempt was made to convert a value from one format type to another,
    although conversions between these format types are not permitted.
    Note that (for the purposes of this error) the format of binary values
    up to length 4 (which can behave as integers) is considered distinct
    from the format of those of length 5 or greater (which cannot).
    Action
    See the Reference documentation for information on format type
    conversion compatibility.

#### NAT6005: The list file is already open.

    Text
    The list file is already open.
    Explanation
    The list file is already open so it cannot be opened again.
    Action
    Close the list file.

#### NAT6007: A program must have less than 40 DO ... DOEND loops.

    Text
    A program must have less than 40 DO ... DOEND loops.
    Explanation
    This program has at least 40 DO ... DOEND loops.
    Action
    Reduce the number of DO ... DOEND loops to less than 40.

#### NAT6008: A program must have less than 5 SETTIME statements.

    Text
    A program must have less than 5 SETTIME statements.
    Explanation
    This program has at least 5 SETTIME statements.
    Action
    Reduce the number of SETTIME statements to less than 5.

#### NAT6009: A program must perform less than 50 different subroutines.

    Text
    A program must perform less than 50 different subroutines.
    Explanation
    This program performs at least 50 different subroutines.
    Action
    Reduce the number of different subroutines performed to less than 50.

#### NAT6010: Operation could not be completed. Memory allocation failed.

    Text
    Operation could not be completed. Memory allocation failed.
    Explanation
    Either the operating system is not configured correctly or there is not
    enough space on the disk for the system swap file. Another possibility
    is that the internal Natural buffer sizes USIZE and SSIZE are too small.
    Check the configuration settings of the operating system and correct
    them if necessary. Then check the available disk space for your system
    swap file. Additionally, check your USIZE and SSIZE settings within
    the Configuration utility and increase them if they seem to be too
    small.
    Action
    Contact your system administrator for further help.

#### NAT6011: Limit of a GP structure exceeded: :1:

    Text
    The limit of a GP structure is exceeded.
    Explanation
    The follwing keywords identify the corresponding GP table structure
    OVFL̲CT:    statement block is too large (IF-THEN-ELSE, loop structure
                etc)
    OVFL̲ADE:   array definition structure too large
    OVFL̲ATT:   field attribute definitions too large
    Action
     Reduce appropiate structure in the Natural program.

#### NAT6012: Internal buffer overflow.

    Text
    Internal buffer overflow.
    Explanation
    Internal error.
    Action
    Contact technical support.

#### NAT6013: Unexpected bufferpool error

    Text
    Unexpected bufferpool error
    Explanation
    Unexpected error when accessing the bufferpool.
    Action
    Restart Natural. If the error occurs again, ask your Natural system
    administrator to restart the Natural bufferpool. If this does not
    help, contact technical Support.

#### NAT6014: Timeout during lock of file

    Text
    Timeout during lock of file
    Explanation
    Locking timeout when trying to open a file.
    Action
    Retry the operation causing the error.

#### NAT6015: WORK FILE number :1: not allocated/available.

    Text
    WORK FILE number ... not allocated/available.
    Explanation
    Work files must have been previously defined by the Natural
    administrator.
    Action
    Make sure that the correct work file number has been used. If it has,
    contact your Natural administrator concerning work file status/usage.

#### NAT6016: Batch input error: :1:.

    Text
    Batch input error: ....
    Explanation
    An INPUT statement in batch mode could not be completed.
    Action
    Make sure that the batch input file is accessible and contains all
    needed data.

#### NAT6017: PC connection already open for workfile :1:

    Text
    PC connection already open for workfile ...
    Explanation
    A transfer to/from a PC was started, while another transfer is already
    active. There can be only one transfer active at any time.
    Action
    Make sure that a transfer is started only when no other one is active.

#### NAT6018: Bad architecture record in the work file :1:, code :2:

    Text
    Bad architecture record in the work file ..., code ...
    Explanation
    While opening a portable work file, a bad architecture record was found.
    This error occurs if the work file is not a portable work file, or it
    has been modified.
    Action
    Make sure that the work file to be read is really a portable work file
    generated by Natural. If the problem persists, call technical support
    and mention the code which occurred.

#### NAT6019: Number of fields wrong, file :1:, record :2:, code :3:.

    Text
    Number of fields wrong, file ..., record ..., code ....
    Explanation
    While reading a portable work file, an invalid length was encountered.
    There are the following reasons for this error:
     1  the number of fields doesn"t match with the READ WORK statement
     2  the length field is corrupted
    Make sure that
    - the fields in the READ WORK statement match the fields in the
      corresponding WRITE WORK statement (including the number of fields,
      scalar/array, etc.)
    - the work file to be read is really a portable work file generated
      by Natural.
    Action
    If the problem persists, call technical support and mention the code
    which occurred.

#### NAT6020: Field mismatch, file :1:, record :2:, field :3:, code :4:.

    Text
    Field mismatch, file ..., record ..., field ..., code ....
    Explanation
    While reading a portable work file, a field which was read does not
    match the specification in the READ WORK statement. The work file
    number, the record number, and the field number are shown in the error
    message. Arrays count as one field here, and must match in the type and
    the number of occurrences.
    The code means:
     1  the field in the READ WORK stmt. is an array, different from file
        record
     2  the field in the file record is an array, different from READ WORK
        stmt.
     3  data type mismatch (e.g., ALPHA and FLOAT)
     4  length mismatch (field length in bytes)
     5  occurrences mismatch of an array field
    Action
    Make sure that the programs match (the write and read work file).

#### NAT6021: Invalid record type, file :1:, record :2:, code :3:.

    Text
    Invalid record type, file ..., record ..., code ....
    Explanation
    While reading a portable work file, an invalid record type was found.
    If the record number and the code are zero, a file has been accessed,
    which is not a portable work file generated by Natural.
    Action
    Make sure that the work file to be read is really a portable work file
    generated by Natural. If the problem persists, call technical support
    and mention the code which occurred.

#### NAT6022: Unexpected END OF FILE, work file :1:.

    Text
    Unexpected END OF FILE, work file ....
    Explanation
    There are 2 reasons for this error:
    - While reading an unformatted work file, an end of file was reached.
      This can happen only if the file is truncated while Natural is reading
      it.
    - While opening/reading a portable work file, an end of file was
      reached.
    Action
    - Make sure that there is no other access to the unformatted work file.
    - Make sure that the work file to be read is really a portable work file
      generated by Natural. If the problem persists, call technical support.

#### NAT6023: Illegal access of work file using dynamic variables.

    Text
    Illegal access of work file using dynamic variables
    Explanation
    The work file types SAG and ENTIRECONNECTION cannot be used with
    dynamic variables.
    Action
    Define the work file with a type which can handle dynamic variables.