Natural System Error Messages 3151-3200

NAT3151: Command-queue overflow. DB/FNR/Net-Work ID :1:/:2:/:3:.

Text
Command-queue overflow. DB/FNR/Net-Work ID .../.../....
Explanation
The database administrator may increase the value for the NC parameter,
and/or the command may be issued when a lower level of command activity
is in effect.

If you are using Entire Net-Work, the leftmost 2 bytes
of the Additions 2 field (Adabas control block) may also
contain the ID of the Entire Net-Work node that issued
this response code.
Action
Contact your database administrator.

NAT3152: Internal user buffer too small. DB/FNR :1:/:2:.

Text
Internal user buffer too small. DB/FNR .../....
Explanation
The internal user buffer was not large enough to contain the user
buffer areas. The database administrator should increase the value
of the LU parameter.
Action
Contact your database administrator.

NAT3153: Previous Adabas call still in process. DB/FNR :1:/:2:.

Text
Previous Adabas call still in process. DB/FNR .../....
Explanation
A 'CALL Adabas' was issued by a user while a previous call for
the user was still being processed.
Action
Contact your database administrator.

NAT3154: Adabas trigger queue overflows. DB/FNR :1:/:2:.

Text
Adabas trigger queue overflows. DB/FNR .../....
Explanation
A command was rejected because it resulted in an Adabas
trigger being fired when the queue was full.
Action
Retry the command, or contact your database administrator.

NAT3155: Pre-command trigger fails. DB/FNR :1:/:2: Name :3:/:4:.

Text
Pre-command trigger fails. DB/FNR .../... Name .../....
Explanation
A command resulted in a pre-command trigger being fired. The
triggered procedure returned a non-zero return-code, so the
command was not executed.
The Name value represents the trigger procedure name, followed
by the error code returned by the procedure.
Action
Contact your database administrator.

NAT3156: Post-command trigger fails. DB/FNR :1:/:2: Name :3:/:4:.

Text
Post-command trigger fails. DB/FNR .../... Name .../....
Explanation
A command resulted in a post-command trigger being fired. The
triggered procedure returns a non-zero return-code, indicating
an unsuccessful execution of the procedure.
The Name value represents the trigger procedure name, followed
by the error code returned by the procedure.
Action
Contact your database administrator.

NAT3157: Adabas trigger facility disabled. DB/FNR :1:/:2:.

Text
Adabas trigger facility disabled. DB/FNR .../....
Explanation
A command resulted in either a pre- or post-command trigger being
fired; however, Adabas triggers have been shut down with the option
to reject all commands that result in a trigger being fired.
Action
See the Adabas Nucleus Messages and Codes documentation for more
information; contact your database administrator.

NAT3159: Adabas link module :1: missing or invalid.

Text
Adabas link module ... missing or invalid.
Explanation
The Adabas link module specified by profile parameter ADANAME
cannot be loaded or is invalid. Either the load library is
missing or invalid or the specified module either doesn't
exist or has been linked incorrectly.
Action
If the Adabas link module should be linked to Natural, then check the
Natural link job. If it shall be dynamically loaded, check the module
name and the load library.

NAT3160: Too many ASSO/DATA blocks active in buffer pool. DB/FNR :1:/:2:.

Text
Too many ASSO/DATA blocks active in buffer pool. DB/FNR .../....
Explanation
Too many Associator and Data Storage blocks were marked as
active in the Adabas buffer pool for a single command.
Action
Contact your database administrator.

NAT3161: Invalid RABN chain in header list. DB/FNR :1:/:2:.

Text
Invalid RABN chain in header list. DB/FNR .../....
Explanation
The RABN chain in the header list of the Adabas buffer pool was
invalid.
Action
Contact your database administrator.

NAT3162: No space for Adabas buffer pool header blocks. DB/FNR :1:/:2:.

Text
No space for Adabas buffer pool header blocks. DB/FNR .../....
Explanation
No additional space was available for Adabas buffer pool header
blocks.
Action
Contact your database administrator.

NAT3163: RABN was already in chain. DB/FNR :1:/:2:.

Text
RABN was already in chain. DB/FNR .../....
Explanation
The RABN to be linked into the RABN header chain was already in
the chain.
Action
Contact your database administrator.

NAT3164: Too many work areas allocated for command. DB/FNR :1:/:2:.

Text
Too many work areas allocated for command. DB/FNR .../....
Explanation
Too many work areas are allocated for the command.
Action
Contact your database administrator.

NAT3165: Descriptor :3: invalid or non-existent. DB/FNR :1:/:2:.

Text
Descriptor ... invalid or non-existent. DB/FNR .../....
Explanation
A descriptor name was either invalid or did not exist in the
Descriptor Value Table. This error may occur during ADAREC
regenerate if
 - a file was loaded with an incorrect FDT, or
 - ADAINV was not re-executed following a stop at a
   SYNP checkpoint.
Bytes 3 and 4 of the Additions 2 field contain the name
of the descriptor that caused the error.
Action
Check program and correct error, or contact your database
administrator. If the problem is not a handling error, run the
INDEX option of ADAVFY and contact Software AG support.

NAT3166: An error was detected in an inverted list index. DB/FNR :1:/:2:.

Text
An error was detected in an inverted list index. DB/FNR .../....
Explanation
The reason for this error may be damage in the associator.
Action
Contact your database administrator.

NAT3167: Field not in coupled file or coupled list invalid. DB/FNR :1:/:2:

Text
Field not in coupled file or coupled list invalid. DB/FNR .../...
Explanation
The field in a coupled file does not exist,
or the coupled list is invalid.








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.

NAT3168: Internal CID for coupling processing not found. DB/FNR :1:/:2:.

Text
Internal CID for coupling processing not found. DB/FNR .../....
Explanation
An internal 'CID' required during coupling processing was not found.
Action
Contact your database administrator.

NAT3170: Adabas RABN for the command could not be found. DB/FNR :1:/:2:.

Text
Adabas RABN for the command could not be found. DB/FNR .../....
Explanation
The Adabas RABN required for the command could not be found.
Action
Contact your database administrator.

NAT3171: The constant set used by Adabas not found. DB/FNR :1:/:2:.

Text
The constant set used by Adabas not found. DB/FNR .../....
Action
Contact your database administrator.

NAT3172: ISN less than MINISN or greater than MAXISN. DB/FNR :1:/:2:.

Text
ISN less than MINISN or greater than MAXISN. DB/FNR .../....
Explanation
An ISN was either less than the MINISN setting or greater than the
MAXISN setting in effect for the file.
Action
Check program and correct error, or contact your database administrator.

NAT3173: An invalid data storage RABN was detected. DB/FNR :1:/:2:.

Text
An invalid data storage RABN was detected. DB/FNR .../....
Action
Contact your database administrator.

NAT3174: Starting RABN for L2/L5 not in address converter. DB/FNR :1:/:2:.

Text
Starting RABN for L2/L5 not in address converter. DB/FNR .../....
Explanation
The starting data storage RABN for an L2/L5 command was not
contained in the address converter for the file.
Action
Check program and correct error, or contact your database administrator.

NAT3175: Index not consistent with Data Storage. DB/FNR :1:/:2:.

Text
Index not consistent with Data Storage. DB/FNR .../....
Explanation
An inconsistency was detected between the index and Data Storage.
Action
Apply the 'check' utilities (especially ADAICK and ADAVAL) to the
file, and contact your Software AG support representative.

NAT3176: Error at inverted list processing. DB/FNR/Subc :1:/:2:/:3:.

Text
Error at inverted list processing. DB/FNR/Subc .../.../....
Explanation
Either an inconsistency in an inverted list was detected or an internal
error occurred during inverted list processing.
The subcode describes the reason of the error.
Action
Check program and correct error, or contact your database administrator.

NAT3177: Record not found in DATA storage block. DB/FNR/Subc :1:/:2:/:3:.

Text
Record not found in DATA storage block. DB/FNR/Subc .../.../....
Explanation
A record could not be found in the Data Storage block which should
have contained it as indicated by the Address Converter.
Action
Contact your database administrator.

NAT3178: Error when updating a field. DB/FNR/Subcode :1:/:2:/:3:.

Text
Error when updating a field. DB/FNR/Subcode .../.../....
Explanation
An internal error occurred when updating a multiple-value field:
1 Inconsistency in descriptor value table (DVT).
2 Inconsistency between the field definition table (FDT)
  and the internal format buffer.
3 Inconsistency when updating a phonetic descriptor.
Action
Contact your database administrator.

NAT3179: Internal error; identifier not found. DB/FNR :1:/:2:.

Text
Internal error; identifier not found. DB/FNR .../....
Explanation
Internal error; identifier could not be found in Work part 3.
Action
For more information, please refer to the Adabas documentation.

NAT3181: Start of transaction not found on autobackout. DB/FNR :1:/:2:.

Text
Start of transaction not found on autobackout. DB/FNR .../....
Explanation
The start of a transaction could not be found when an
'autobackout' was executed.
Action
Check program and correct error, or contact your database administrator.

NAT3182: Necessary ET data were not found in WORK block. DB/FNR :1:/:2:.

Text
Necessary ET data were not found in WORK block. DB/FNR .../....
Explanation
The necessary ET data were not found in the appropriate WORK block.
Action
Correct error or contact your database administrator.

NAT3183: Internal number for database I/O operation invalid.DB/FNR :1:/:2:

Text
Internal number for database I/O operation invalid.DB/FNR .../....
Explanation
An internally assigned number for a for a database I/O operation was
found to be invalid.
Action
Contact your database administrator.

NAT3184: A phonetic field name could not be found. DB/FNR :1:/:2:.

Text
A phonetic field name could not be found. DB/FNR .../....
Action
Check program and correct error, or contact your database administrator.

NAT3185: ADAM field not found in the compressed record. DB/FNR :1:/:2:.

Text
ADAM field not found in the compressed record. DB/FNR .../....
Action
Contact your database administrator.

NAT3196: Referential integrity violated (DB/FNR/sub/con :1:/:2:/:3:/:4:).

Text
Referential integrity violated (DB/FNR/sub/con .../.../.../...).
Explanation
The command has been rejected by Adabas.
Referential integrity has been violated. The error message shows
the database ID, file number, subcode and constraint name of the
violated constraint.
Action
Handle the referential integrity violation;
for example, by issuing an appropriate error message.

NAT3197: Pool for unique descriptor values too small.DB/FNR :1:/:2:.

Text
Pool for unique descriptor values too small.DB/FNR .../....
Action
Contact your database administrator.

NAT3198: Value for descriptor :4: already exists. DB/FNR/Subc :1:/:2:/:3:.

Text
Value for descriptor ... already exists. DB/FNR/Subc .../.../....
Explanation
An attempt was made to duplicate a value for a unique descriptor.
The leftmost 2 bytes of the Additions 2 field may contain the
descriptor name.
Action
Check program and correct error, or contact your database administrator.

NAT3199: Error in inverted list index for field :3:. DB/FNR :1:/:2:.

Text
Error in inverted list index for field .... DB/FNR .../....
Explanation
During an UPDATE operation, an inconsistency was detected in an
inverted list index. The leftmost 2 bytes of the Additions 2
field may contain the descriptor name. This response code
can also occur if UTYPE=EXU was specified for an ADARES
BACKOUT operation that uses the sequential (SIBA) log.
Action
Contact your database administrator.

NAT3200: Security violation. DB/FNR/Subcode :1:/:2:/:3:.

Text
Security violation. DB/FNR/Subcode .../.../....
Explanation
Either an invalid cipher code or an Adabas or Adabas SAF Security
security violation was detected.
From Adabas SAF Security processing, the command could not satisfy the
necessary security checks and may be accompanied by a subcode as
follows:
0 A standard user check failed.
1 There is no free user file cache entry for a workstation user.
2 A cross-level security check failed.
3 No security information is available for the command.
4 A time-out occurred during a workstation logon.
Action
Check program and correct error, or contact your database administrator.