Natural System Error Messages 3051-3100

NAT3051: Error in record buffer. DB :1:.

Text
Error in record buffer. DB ....
Explanation
An error in the record buffer was detected during processing
of an OP command.
Action
Correct the record buffer by changing the OPRB parameter.

NAT3052: Error processing a buffer. DB/FNR/Subc/Name :1:/:2:/:3:/:4:.

Text
Error processing a buffer. DB/FNR/Subc/Name .../.../.../....
Explanation
An error occurred while processing the record buffer, value buffer,
or search buffer:
- The value of a P format field was not in packed decimal format.
- The value of a U format field was not in unpacked decimal format.
- A variable-length field was specified without a length parameter.
- A field defined with the 'no null value' (NC/NN) option was
  found to contain no value or a null value, or an attempt was
  made to store such a value in the field.
Action
Check program and correct error.

NAT3053: Wrong record buffer size. DB/FNR/Subcode :1:/:2:/:3:.

Text
Wrong record buffer size. DB/FNR/Subcode .../.../....
Explanation
The record buffer is too small to contain all required Adabas values
in compressed form; or the record buffer size does not correspond
to the record-buffer size of the global format ID (GFID) already
established in Adabas. Or the ISN buffer is too small.
Action
Check program and correct error; or first recatalog the local data area
(LDA) that contains the view to which the GFID is assigned, and then
recatalog all programs which use this LDA.

NAT3054: Record buffer too long. DB/Subcode :1:/:2:.

Text
Record buffer too long. DB/Subcode .../....
Explanation
The record buffer for a C3, C5 or ET command was too long.
A maximum of 2048 bytes can be written to the checkpoint file.
The following subcodes (in hexadecimal) may be indicated.

1 The record buffer for the C3 command is too long.
2 The record buffer for the C5 command is too long.
3 The record buffer for the ET command is too long.
Action
Check program and correct error, or contact your database administrator.

NAT3055: Conversion not possible. DB/FNR/Subcode :1:/:2:/:3:.

Text
Conversion not possible. DB/FNR/Subcode .../.../....
Explanation
An attempted format conversion was not possible due to incompatible
data formats or other compatibility problems.

During a read-type operation, a field defined with the SQL null (NC)
option contained a null value, but the format buffer held no 'S'
(significant null) indicator field. Additions 2  may contain the
field name in the leftmost two bytes; the rightmost two bytes may
contain the offset into the record buffer.
Action
Correct error in program, or contact your database administrator.

NAT3056: Descriptor value too long. DB/FNR/Subcode :1:/:2:/:3:.

Text
Descriptor value too long. DB/FNR/Subcode .../.../....
Explanation
One of the following occurred:

- The descriptor value was too long.
- The collation value exceeds the maximum of 253 bytes. The
  subcode 'n' is the collation descriptor exit number.
Action
Check program and correct error.

NAT3057: Invalid descriptor specified in search buffer. DB/FNR :1:/:2:.

Text
Invalid descriptor specified in search buffer. DB/FNR .../....
Explanation
The descriptor specified in the search buffer of the L9 command
was invalid.
Action
Check program and correct error.

NAT3058: The format could not be found. DB/FNR :1:/:2:.

Text
The format could not be found. DB/FNR .../....
Explanation
The format - as defined within format selection criteria - could not
be found.
Action
Check program and correct error.

NAT3059: Format conversion of a subfield is not possible. DB/FNR :1:/:2:.

Text
Format conversion of a subfield is not possible. DB/FNR .../....
Action
Check program and correct error.

NAT3060: Syntax error at field :4:. DB/FNR/Subcode :1:/:2:/:3:.

Text
Syntax error at field .... DB/FNR/Subcode .../.../....
Explanation
A syntax error was detected in the format or search buffer.
Generally the first two bytes of the Additions 2 field contain
the two characters under inspection when the error was detected.
For a detailed explanation of the error, see the documentation
for the subcode (also in the rightmost two bytes of the
Additions 2 field).
Action
Check program and correct error.

NAT3061: Error in search buffer. DB/FNR/Subcode :1:/:2:/:3:.

Text
Error in search buffer. DB/FNR/Subcode .../.../....
Explanation
The cause of error may be:
- The order of elements was invalid.
- The specified field was not a descriptor.
- An index was missing or invalid.
- Invalid connection of partial criteria.
- Invalid use of a phonetic descriptor.
- The length of a descriptor value was greater than 253.
- An invalid file number.
- An invalid range specification.

For the detailed reason, see the subcode.
Action
Check program and correct error.

NAT3062: Search/value buffer length too short. DB/FNR :1:/:2:.

Text
Search/value buffer length too short. DB/FNR .../....
Explanation
The length of the search buffer and/or value buffer, as specified in
the search and value buffer length fields, was too short to accommodate
the search criteria specified;
or the first character in the search buffer was a '.';
or the search buffer does not contain a '.'.
Action
Check program and correct error.

NAT3063: CID value specified in search buffer not found. DB/FNR :1:/:2:.

Text
CID value specified in search buffer not found. DB/FNR .../....
Explanation
The CID value specified in the search buffer was not found.
Action
Check program and correct error.

NAT3064: Requested function cannot be performed. DB/FNR/Sub :1:/:2:/:3:.

Text
Requested function cannot be performed. DB/FNR/Sub .../.../....
Explanation
The requested function cannot be performed on Adabas system files.
Action
Refer to the ADAREP output report for a list of the system files.

NAT3065: Internal error. DB/FNR :1:/:2:.

Text
Internal error. DB/FNR .../....
Explanation
An internal error has occurred: the Adabas nucleus has detected an
error in space calculation.
Action
Contact your database administrator.

NAT3066: An incompatible owner ID was detected. DB/FNR :1:/:2:.

Text
An incompatible owner ID was detected. DB/FNR .../....
Explanation
An incompatible owner ID was detected during an update operation on a
multi-client file. The owner ID may be blank, or too long.
Action
For more information, please refer to the Adabas documentation.

NAT3067: Internal error. DB/FNR/Subcode :1:/:2:/:3:.

Text
Internal error. DB/FNR/Subcode .../.../....
Explanation
An internal error has occurred while an Adabas Sx command was being
executed. Or an error occurred during superfield generation.
Action
Retain all related information, and contact Software AG support.

NAT3068: Incompatible owner ID or non-descriptor search. DB/FNR :1:/:2:.

Text
Incompatible owner ID or non-descriptor search. DB/FNR .../....
Explanation
One of the following has occurred:
- An incompatible owner ID was detected during an update
  operation on a multiclient file. The owner ID may be blank
  or too long.
- A non-descriptor field was used as a search criterion, and
  the non-descriptor search facility has been set off (the
  default for this facility is 'on').
Action
Check the owner ID of any multiclient file's update operation.
Otherwise, remove non-descriptor searches from your application

NAT3070: Overflow in the table of sequential commands. DB/FNR :1:/:2:.

Text
Overflow in the table of sequential commands. DB/FNR .../....
Explanation
The database administrator may increase the value used for
the LQ parameter, and/or RC commands may be used to release elements.
Action
Contact your database administrator.

NAT3071: Overflow in the table of resulting ISN lists. DB/FNR :1:/:2:.

Text
Overflow in the table of resulting ISN lists. DB/FNR .../....
Explanation
The database administrator may increase size of the value used for
the LI parameter, and/or RC commands may be used to release elements.
Action
Contact your database administrator.

NAT3072: User queue overflow. DB/FNR/Subcode :1:/:2:/:3:.

Text
User queue overflow. DB/FNR/Subcode .../.../....
Explanation
An overflow occurred in the user queue or the user file list pool.
Action
Ask your database administrator to increase the value
used for the NU parameter.

NAT3073: Overflow in WORK dataset for resulting ISN lists. DB/FNR :1:/:2:.

Text
Overflow in WORK dataset for resulting ISN lists. DB/FNR .../....
Explanation
An overflow occurred in the section of the WORK dataset in which
resulting ISN lists are stored.
The database administrator may increase the size of the WORK dataset,
and/or the number of ISN lists saved during an Adabas session may be
decreased.
Action
Contact your database administrator.

NAT3074: No space on WORK dataset for complex FIND commands.DB/FNR :1:/:2:

Text
No space on WORK dataset for complex FIND commands.DB/FNR .../....
Explanation
No space was available on the WORK dataset for complex FIND commands.
The database administrator may increase the size of the WORK dataset.
Action
Contact your database administrator.

NAT3075: No more ASSO/DATA extents available. DB/FNR :1:/:2:.

Text
No more ASSO/DATA extents available. DB/FNR .../....
Explanation
Attempts to allocate additional logical file extents for a file were
issued, but the maximum that can be handled by the FCB has already
been allocated. BT or autorestart could cause the file to be locked
because of inadequate extent space (see response code 48).







For an explanation of this response code for non-mainframe databases,
see the Adabas documentation.
Action
Ask the DBA for assistance; Associator or Data Storage extents may have
to be reallocated.

NAT3076: An overflow occurred in an inverted list index. DB/FNR :1:/:2:.

Text
An overflow occurred in an inverted list index. DB/FNR .../....
Explanation
The maximum is six levels.
Action
Contact your database administrator.

NAT3077: Not enough space for extent. DB/FNR/Subcode :1:/:2:/:3:.

Text
Not enough space for extent. DB/FNR/Subcode .../.../....
Explanation
A file needed a new associator or data storage extent,
but there was not enough space available for such an extent.
For a detailed explanation of the error, see the documentation
of the subcode.
Action
Contact your database administrator.

NAT3078: AC file cannot be increased. DB/FNR/Subcode :1:/:2:/:3:.

Text
AC file cannot be increased. DB/FNR/Subcode .../.../....
Explanation
This error may be caused by one of the following:

- The AC file cannot be increased; only one file extent is permitted.

- The file contains more than 16 MB of ISNs.
Action
Contact your database administrator. If the file has reached the
16-MB limit, you might convert it to a file with the 4-byte ISN
option or to an expanded file.

NAT3079: Descriptor exit error occurred. DB/FNR/Subcode :1:/:2:/:3:.

Text
Descriptor exit error occurred. DB/FNR/Subcode .../.../....
Explanation
A collation descriptor exit or hyperexit error occurred.
The reason is described by the subcode.

For more information, see the Adabas documentation.
Action
Contact your database administrator.

NAT3081: Mult.-value field/periodic group error. DB/FNR/Sub :1:/:2:/:3:.

Text
Mult.-value field/periodic group error. DB/FNR/Sub .../.../....
Explanation
An error with a multiple-value field (MU) or periodic group (PE)
occurred. The subcode (Sub) indicates the cause of the error:

1 The PE index is greater than 191 (if the maximum number of PE
  field occurrences is 191).
2 The PE index is greater than 65534 (if the maximum number of PE
  field occurrences is 65534).
3 The MU index is greater than 65534 (if the maximum number of MU
  field occurrences is 65534).
4 The MU index is greater than 191 (if the maximum number of MU
  field occurrences is 191).
Action
Correct the MU or PE field problem and try again.

NAT3082: Hyperexit routine returned invalid ISN. DB/FNR :1:/:2:.

Text
Hyperexit routine returned invalid ISN. DB/FNR .../....
Explanation
A hyperexit routine returned an invalid ISN.
Action
Check program and correct error, or contact your database administrator.

NAT3083: Hypertable overflow. DB/FNR :1:/:2:.

Text
Hypertable overflow. DB/FNR .../....
Explanation
A hypertable overflow has occurred.









For an explanation of this response code for non-mainframe databases,
see the Adabas documentation.
Action
Contact your database administrator.

NAT3084: Too many values for a sub- or superdescriptor. DB/FNR :1:/:2:.

Text
Too many values for a sub- or superdescriptor. DB/FNR .../....
Explanation
Too many values were present for a subdescriptor or a superdescriptor.
Action
Check program and correct error, or contact your database administrator.

NAT3085: Too many descriptor values for UPDATE/ADD RECORD. DB/FNR :1:/:2:.

Text
Too many descriptor values for UPDATE/ADD RECORD. DB/FNR .../....
Explanation
Too many descriptor values were present for an UDPATE or ADD RECORD
command.








For an explanation of this response code for non-mainframe databases,
see the Adabas documentation.
Action
Check program and correct error, or contact your database administrator.

NAT3086: Hyperdescriptor exit return error. DB/FNR :1:/:2:.

Text
Hyperdescriptor exit return error. DB/FNR .../....
Explanation
Possible reasons:
- An incorrect sign for a packed descriptor value was created.
- A value with an incorrect length byte was returned.
Action
Contact your database administrator.

NAT3087: Adabas buffer pool length error. DB/FNR/Subcode :1:/:2:/:3:.

Text
Adabas buffer pool length error. DB/FNR/Subcode .../.../....
Explanation
An Adabas buffer pool of ADASMP multi-processing global buffer
pool error has occurred:
- the Adabas buffer pool is locked; it is too small to accommodate
  all blocks needed for (parallel) command execution;
- the ADASMP global buffer pool is too small.

The ADASMP global buffer pool size, specified by the ADASMP
initialization parameter LGBP, must be at least four times as
large as the ADARUN LBP parameter for the read/write nucleus.
See the Adabas DBA Reference documentation for more information.
Action
Contact your database administrator to increase the LBP or LGBP;
then retry the operation.
If the error occurs again, contact Software AG support.

NAT3088: Insufficient core in Adabas workpool. DB/FNR :1:/:2: Subcode :3:.

Text
Insufficient core in Adabas workpool. DB/FNR .../... Subcode ....
Explanation
During the execution of a database command, Adabas has indicated a
workpool shortage. The detailed reason is indicated by
the subcode:
  1: Sufficient LWP workpool space was not available.
  2: The space or hold queue resources needed to execute the command
     could not be acquired.
  4: There are space problems in the workpool during update.
For a more detailed description, see the Adabas
documentation.
Action
Increase the value of the LWP parameter.

NAT3089: UQE already used. DB/FNR :1:/:2:.

Text
UQE already used. DB/FNR .../....
Explanation
The UQE was already in use, and an attempt was made to execute
two commands and the same time for the same user.
Action
Contact your database administrator.

NAT3094: An I/O error occurred on DDWORKR4. DB/FNR :1:/:2:.

Text
An I/O error occurred on DDWORKR4. DB/FNR .../....
Explanation
An I/O error occurred on DDWORKR4.
Action
Contact your database administrator.

NAT3095: An I/O error occurred in the WORK LP area. DB/FNR :1:/:2:.

Text
An I/O error occurred in the WORK LP area. DB/FNR .../....
Action
Contact your database administrator.

NAT3096: Error during repair execution. DB/FNR/Subcode :1:/:2:/:3:.

Text
Error during repair execution. DB/FNR/Subcode .../.../....
Explanation
An error occurred during an ADARES repair execution.
Action
Contact your database administrator.

NAT3097: An I/O error occurred during buffer flush. DB/FNR :1:/:2:.

Text
An I/O error occurred during buffer flush. DB/FNR .../....
Action
Contact your database administrator.

NAT3098: Value to be added already exists. DB/FNR :1:/:2:.

Text
Value to be added already exists. DB/FNR .../....
Explanation
An attempt was made to add to a unique descriptor a value
which already exists.
Action
Check program and correct error, or contact your database administrator.

NAT3099: An I/O error occurred. DB/FNR :1:/:2:.

Text
An I/O error occurred. DB/FNR .../....
Action
Contact your database administrator.