Adabas Transaction Manager Messages and Codes - Software AG ...

Response 161
Origin
Explanation
Response 162
Origin
Explanation
Action
Response 163
Origin
Explanation
Response 164
Origin
Explanation
Response 165
Origin
Explanation
Action
Mainframe systems only
The RABN chain in the header list of the Adabas buffer pool is invalid.
Mainframe and open systems
No additional space is available for the Adabas buffer pool.
Increase the value of the ADARUN LBP parameter.
On open systems, because the buffer pool overflow is normally caused by too many blocks
in the buffer pool waiting to be written to disk, specifying a low value for the WRITE_LIMIT
parameter is recommended.
Mainframe systems only
The RABN to be linked into the RABN header chain is already in the chain.
Mainframe systems only
Too many work areas were allocated for the command.
Mainframe and open systems
A descriptor name was either invalid or did not exist in the descriptor value table (DVT).
For expanded files: the descriptor does not exist on all component files.
On open systems, this error may occur during ADAREC generate if one of the following
occurs:
■ A file was loaded with an incorrect FDT.
■ ADAINV was not reexecuted following a stop at a SYNP checkpoint.
In an ACB, the leftmost two bytes of Additions 2 may contain the descriptor name; in an
ACBX, the Error Character Field (ACBXERRB) may contain the descriptor name. If this
occurred for an expanded file, check to see if there is an FDT mismatch between the
components of the file.
On open systems, bytes 3 and 4 of the Additions 2 field contains the name of the descriptor
that caused the error.
On open systems, if the error is not a handling error, run the INDEX option of ADAVFY
and contact your Software AG technical support representative.
Adabas Transaction Manager Messages and Codes
Adabas Response Codes
141