Natural System Error Messages 3000-3049

#### Search Results

Search

# Natural System Error Messages 3000-3049

#### NAT3000: A non-zero response code was received from the database.

    Text
    A non-zero response code was received from the database.
    Explanation
    The Natural error messages NAT3001 - NAT3999 deal with database response
    codes; that is, an error message "NAT3nnn" indicates that the database
    has replied to a command with a response code "nnn".
    The error may be caused by one of the following:
    - An invalid request was made to the database.
    - A malfunction occurred in the database.
    Action
    Retain the number of the response code and contact your database
    administrator.

#### NAT3001: ISN list not sorted. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    ISN list not sorted. DB/FNR/Subcode .../.../....
    Explanation
    The following subcodes may be indicated:
    1  An online SAVE operation requires a PLOG.
    2  The selected record is not allowed.
    3  S2 command did not have enough space.
    4  S2/S9 internal program error.
    5  System was not in save status at the end of an online ADASAV.
    Action
    Increase the ADARUN LS parameter value.

#### NAT3002: Record not held. DB/Subcode :1:/:2:.

    Text
    Record not held. DB/Subcode .../....
    Explanation
    ISNs could not be held because of insufficient space in the hold queue.
    Action
    Contact your database administrator.

#### NAT3003: End-of-file detected. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    End-of-file detected. DB/FNR/Subcode .../.../....
    Explanation
    The following subcodes may be indicated:
    1  An end-of-file or end-of-list condition was detected (L3/L6 on a
       non-expanded file).
    4  End of LOB value reached. An attempt was made to read a LOB value
       segment that begins after the end of the value. This response code/
       subcode is given to an L1/L4 command with Command Option 2 set to L
       if the ISN Lower Limit value is greater than or equal to the length
       of the LOB value being read.
    66 A program tried to read or change a multiclient file"s record using
       either a blank or incorrect-length owner ID, or an owner ID that is
       not allowed for the record.
    Action
    For more information, please refer to the Adabas documentation.

#### NAT3004: The internal Adabas TRS storage directory is full.

    Text
    The internal Adabas TRS storage directory is full.
    Explanation
    The internal Adabas TRS storage directory is full.
    Action
    Free some of the active queries.

#### NAT3007: Sx command interrupted due to time limit. DB/FNR :1:/:2:.

    Text
    Sx command interrupted due to time limit. DB/FNR .../....
    Explanation
    An Sx command has been interrupted because the maximum amount of time
    permitted has been exceeded.
    Action
    Contact your database administrator.

#### NAT3008: Command interrupted to prevent WORK overflow. DB/FNR :1:/:2:.

    Text
    Command interrupted to prevent WORK overflow. DB/FNR .../....
    Explanation
    The command was interrupted to prevent a WORK overflow
    because of a pending backout operation.
    Action
    The value specified for the LP parameter might have to be
    increased.

#### NAT3009: Last transaction backed out of database :1:. Subcode :2:.

    Text
    Last transaction backed out of database .... Subcode ....
    Explanation
    The last transaction has been backed out by Adabas because an Adabas
    time limit has been exceeded or because of a security violation.
    This error may also occur if an Adabas OP command is required
    (Adabas parameter OPENRQ=YES) but an Adabas command was issued
    without an OP command having been issued before.
    For the detailed reason see the subcode.
    Action
    Correct cause of time-out or security violation, and execute transaction
    again; or issue OP command correctly.

#### NAT3010: Too many occurrences for periodic group. DB/FNR :1:/:2:.

    Text
    Too many occurrences for periodic group. DB/FNR .../....
    Explanation
    Too many occurrences for a periodic group.
    Action
    Check program and correct error.

#### NAT3016: An error occurred in an MC call processing. DB/FNR :1:/:2:.

    Text
    An error occurred in an MC call processing. DB/FNR .../....
    Explanation
    An error occurred in an MC call during subcommand processing.
    Action
    Contact your database administrator.

#### NAT3017: Invalid file number. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Invalid file number. DB/FNR/Subcode .../.../....
    Explanation
    The file number was invalid. Possible causes are:
     - The file number was either 0 or greater than the maximum allowed.
     - The file was not in the database.
     - The file was locked.
     - A required Adabas system file was not loaded.
    Make sure that you use the correct file number.
    Action
    For more information, please refer to the Adabas documentation.

#### NAT3018: Incorrect usage of file number. DB/FNR :1:/:2:.

    Text
    Incorrect usage of file number. DB/FNR .../....
    Explanation
    The file number was modified between successive L2/L5 calls.
    Action
    Check program and correct error.

#### NAT3019: Update not permitted for access-only file. DB/FNR :1:/:2:.

    Text
    Update not permitted for access-only file. DB/FNR .../....
    Explanation
    An attempt was made to update a file which was opened for access only.
    Action
    Check program and correct error.

#### NAT3020: Incorrect entry made for a command ID value. DB/FNR :1:/:2:.

    Text
    Incorrect entry made for a command ID value. DB/FNR .../....
    Explanation
    One of the following incorrect entries was used for a command ID value:
     - binary zeros;
     - blanks;
     - the high-order byte contains the hexadecimal value "FF", but there is
       no automatic command ID generation;
     - the three high-order bytes contain the ASCII string "SYN".
    Action
    Check program and correct error.

#### NAT3021: An invalid CID value was detected. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    An invalid CID value was detected. DB/FNR/Subcode .../.../....
    Explanation
    A time-out occurred because a command ID was not found.
    This program error can be caused by:
     - the CMD ID being assigned to another Lx command;
     - the CMD ID being assigned to another file;
     - the CMD ID was not found for an Sx command.
    Action
    Check program and correct error.
    For more information, please refer to the Adabas documentation.

#### NAT3022: Invalid command :4:. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Invalid command .... DB/FNR/Subcode .../.../....
    Explanation
    The command or command option is invalid. Some possible subcodes:
    1/1005         Invalid command code.
    2              Access-only user attempted to issue an update command.
    18             ADALNK X"48" call logic has been suppressed.
    21             Non-ET-logic user issued BT command.
    52             A non-Adabas target was called.
    1006/1007/1008 Invalid ACBX/ABD/ABD-type.
    1010/1011      More than one value buffer/ISN buffer specified.
    1012/1013      Number of search and value buffers/format and record
                   buffers do not match.
    Action
    Check program and correct error.
    For more information, please refer to the Adabas documentation.

#### NAT3023: Invalid starting ISN specified. DB/FNR :1:/:2:.

    Text
    Invalid starting ISN specified. DB/FNR .../....
    Explanation
    The starting ISN specified for an L2/L5 command sequence was invalid:
     - The ISN is not assigned to a record in the file.
     - The ISN was greater than the MAXISN in effect for the file.
    Action
    Check program and correct error.

#### NAT3024: Invalid ISN in complex FIND SORTED statement. DB/FNR :1:/:2:.

    Text
    Invalid ISN in complex FIND SORTED statement. DB/FNR .../....
    Explanation
    This error may be caused by one of the following:
       - The ISN list in the ISN buffer was already sorted.
       - The ISN list in the ISN buffer contained an invalid ISN.
       - The "D" option was specified when trying to sort by ISN.
    Action
    Check program and correct error,
    or contact your database administrator.

#### NAT3025: ISN in ISN lower limit for S1/S4 not found. DB/FNR :1:/:2:.

    Text
    ISN in ISN lower limit for S1/S4 not found. DB/FNR .../....
    Explanation
    The ISN specified in ISN Lower Limit for an S1/S4 (or S2/S9) command
    was not found.
    Action
    Check program and correct error.

#### NAT3026: Invalid ISN buffer length. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Invalid ISN buffer length. DB/FNR/Subcode .../.../....
    Explanation
    An invalid ISN buffer length for an S9 command was detected.
    The number of ISNs to be sorted as provided in ISN quantity is zero.
    Possible subcodes:
    2  The ISN buffer of the S9 command contains ISNs that are higher than
       the TOP-ISN of the file.
    Action
    Check program and correct error.

#### NAT3027: Search/value buffer overflow. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Search/value buffer overflow. DB/FNR/Subcode .../.../....
    Explanation
    There was not enough work space available to either accommodate the
    combined sizes of the search and value buffers as indicated in the
    fields Search Buffer Length and Value Buffer Length,
    or generate the format translation.
    Action
    Check program and correct error.

#### NAT3028: Invalid descriptor :4:. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Invalid descriptor .... DB/FNR/Subcode .../.../....
    Explanation
    A descriptor was invalid for an L3/L6 or S2/S9 command.
    The following subcodes may be indicated:
     1 The field was not a descriptor.
     2 The descriptor is contained within a periodic group.
     3 The descriptor was changed between successive calls.
     4 The Additions 1 field contained a different descriptor than
       the descriptor contained in the search buffer.
     5 An initial L3/L6 call contains no trailing blanks in the Additions 1
       field.
    Action
    Check program and correct error.
    For more information, please refer to the Adabas documentation.

#### NAT3029: Incorrect value repositioning attempted. DB/FNR :1:/:2:.

    Text
    Incorrect value repositioning attempted. DB/FNR .../....
    Explanation
    A value repositioning was attempted with an L3/L6 command (bytes 7-8
    of the Additions 1 field contain spaces) and the Command Option 2 field
    did not contain the value "V".
    The command ID is released.
    Action
    Check program and correct error.

#### NAT3034: An invalid command option has been detected. DB/FNR :1:/:2:.

    Text
    An invalid command option has been detected. DB/FNR .../....
    Explanation
    An invalid command option has been detected
    for the database ID / file number indicated in the error message.
    Action
    Either remove the invalid command option or replace it with a valid
    option. See the Adabas documentation for more information.

#### NAT3035: Invalid function for non-cluster Adabas nucleus. DB/FNR :1:/:2:.

    Text
    Invalid function for non-cluster Adabas nucleus. DB/FNR .../....
    Explanation
    The user/DBA attempted to perform a function for a non-cluster Adabas
    nucleus that is available only for an Adabas cluster database.
    Action
    Do not perform this function for this type of nucleus.

#### NAT3039: Logically deleted descriptor used as search crit. DB/FNR :1:/:2:

    Text
    Logically deleted descriptor used as search crit. DB/FNR .../...
    Explanation
    A logically deleted descriptor was used as a search criterion
    or was specified in the first two bytes of the Additions 1 field
    for an L3, L6, L9, S2, or S9 command.  DB/FNR .../....
    Action
    Remove the use of the logically deleted descriptor and inform your
    database administrator about the problem.

#### NAT3040: Syntax error in format buffer. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Syntax error in format buffer. DB/FNR/Subcode .../.../....
    Explanation
    The syntax error may be one of the following:
     - The terminating period was missing.
     - The first position contains a period.
     - Length and/or format was specified with a range definition.
     - An invalid element was detected.
     - The L9 descriptor name in the search buffer did not agree with
       the name in the format buffer.
    Action
    Check program and correct error.

#### NAT3041: Error in format buffer. DB/FNR/Subc/Field :1:/:2:/:3:/:4:.

    Text
    Error in format buffer. DB/FNR/Subc/Field .../.../.../....
    Explanation
    The following subcodes may be indicated:
     1 Spacing element nX with n=0 or n>255 not allowed.
     2 Invalid sequence of format buffer elements was specified.
     3 Specification errors in the format buffer.
     4 A field name was undefined or not elementary.
     5 Format without fields.
     6 A group field cannot be specified if the group contains a LOB (LB)
       field.
     7 A field name is undefined.
    24 A phonetic, collation, or hyperdescriptor was specified.
    Further subcodes are described in the Adabas documentation.
    The message shows the name of the field being processed when the error
    was detected.
    Action
    Check program and DDM and correct error.

#### NAT3042: Internal buffer too small. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Internal buffer too small. DB/FNR/Subcode .../.../....
    Explanation
    A space problem occurred. The following are the subcodes and their
    meanings:
    1  The Work pool was too small to store a user format.
    2  The internal format buffer was too small to store a user format
       (translated into internal structure).
    Action
    Subcode 1: Increase the LWP specification and retry.
    Subcode 2: Increase the LFP specification and retry.

#### NAT3043: Descriptor in format and search buffer not equal. DB/FNR :1:/:2:.

    Text
    Descriptor in format and search buffer not equal. DB/FNR .../....
    Explanation
    The descriptor specified in the format buffer did not agree with the
    descriptor specified in the search buffer.
    Action
    Check program and correct error.

#### NAT3044: Invalid format buffer. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Invalid format buffer. DB/FNR/Subcode .../.../....
    Explanation
    The following subcodes may be indicated:
    1/3 Invalid format for update operation, e.g. a conditional format
        buffer with an update operation.
    2/4 The L9"s format buffer format is not allowed for other commands.
    5   Format used for L9 can only contain field and an optional daylight
        savings time indicator (fldD).
    6   Fixed point format must have length 2, 4, or 8.
    7   Conditional format and more than one format buffer was specified.
    8   The current Adabas call provides a different number of format
        buffers than the format reference by CID.
    9   Number of format buffer segments (ABDs) is zero.
    Action
    Check program and DDM and correct error.
    For more information, please refer to the Adabas documentation.

#### NAT3045: Adabas internal format buffer space exceeded. DB/FNR :1:/:2:.

    Text
    Adabas internal format buffer space exceeded. DB/FNR .../...
    Explanation
    The Adabas internal format buffer space has been exceeded. Either the
    Adabas LWP parameter setting is too small, or the internal format buffer
    requires more than 2GB.
    For an explanation of this response code for non-z/OS databases,
    see the Adabas documentation.
    Action
    Contact your database administrator.

#### NAT3046: Maximum value for Adabas NQCID exceeded. DB/FNR :1:/:2:.

    Text
    Maximum value for Adabas NQCID exceeded. DB/FNR .../....
    Explanation
    The maximum value for the Adabas parameter NQCID was exceeded.
    For an explanation of this response code for non-mainframe databases,
    see the Adabas documentation.
    Action
    Contact your Adabas administrator.

#### NAT3047: Maximum value for Adabas parm NISNHQ exceeded. DB/FNR :1:/:2:.

    Text
    Maximum value for Adabas parm NISNHQ exceeded. DB/FNR .../....
    Action
    Contact your database administrator.

#### NAT3048: Error during Open processing. DB/Subcode :1:/:2:.

    Text
    Error during Open processing. DB/Subcode .../....
    Explanation
    An error occurred during the processing of a command such as OP or N1.
    The default reason for this response code is that files are not
    available at open time. Other reasons are indicated by a subcode:
     1 A specified file is locked against the requested use.
     2 A specified file is currently in conflicting use.
     4 The file is locked or in exclusive control by another user.
     8 The user ID provided in the OP command is already assigned to another
       user.
    11 A non-privileged user issued an open (OP) command to a nucleus that
       is in UTIONLY (utilities only) status.
    17 The data of a specified file is not accessible. This can happen if a
       utility aborts or an autorestart fails.
    Further subcodes are described in the Adabas documentation.
    Action
    See the documentation for nucleus response codes, or
    contact your database administrator.

#### NAT3049: Compressed record too long. DB/FNR/Subcode :1:/:2:/:3:.

    Text
    Compressed record too long. DB/FNR/Subcode .../.../....
    Explanation
    The compressed record was too long. It exceeds the maximum
    permitted record length for the file. The following subcodes
    may be indicated.
    1  Multiple-value (MU) field.
    2  Periodic (PE) group field.
    3  MU field.
    4  PE group.
    5  PE group level.
    6  Remaining fields.
    10 Long alpha or wide field.
    Default message:  File(s) not available at open time.
    Further subcodes are described in the Adabas documentation.
    Action
    Contact your database administrator.