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

Response 168
Origin
Explanation
Response 170
Origin
Explanation
Action
Response 171
Origin
Explanation
Response 172
Origin
Explanation
1. Locate the descriptor that caused the error in the Additions 2 field of the user control
block;
2. Run the VERIFY option of ADAINV for this descriptor and save the output;
3. Reinvert the descriptor;
4. If necessary, restart the database (if this is possible);
5. Send the following information to your nearest support center:
■ The output of the VERIFY option of ADAINV;
■ All available PLOGs;
■ The FDT of the file containing the error;
■ If the nucleus crashed, the crash directory.
Mainframe systems only
An internal command ID required during coupling processing was not found.
Mainframe and open systems
The Adabas RABN required for the command could not be located for one of the following
reasons:
■ The buffer segment was called with a RABN of zero.
■ The specified RABN does not belong to this database and is invalid.
On open systems, the Additions 2 field contains the invalid RABN in 4 byte binary format.
On open systems, run the LOST, INDEX and DATA options of ADAVFY for the file in
question and contact your Software AG technical support representative.
Mainframe systems only
The constant set used by Adabas could not be located.
Mainframe and open systems
On mainframe systems, an ISN was less than the MINISN or greater than the MAXISN
setting in effect for the file.
On open systems, the maximum possible ISN of the file was reached and no more can be
allocated.
Adabas Transaction Manager Messages and Codes
Adabas Response Codes
143