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

Adabas Response Codes
Response 166
Origin
Explanation
Action
Response 167
Origin
Explanation
Action
142
Mainframe and open systems
An error was detected in an inverted list index; a descriptor value was not found during a
delete operation. The cause may be damage in the Associator.
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 perform the following steps:
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 Software AG technical support representative:
■ 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 and open systems
The meaning of this response code varies, depending on whether you are using Adabas on
mainframe systems or Adabas on open systems.
Mainframe Systems
The field in a coupled file does not exist or the coupled list is invalid.
Open Systems
An error was detected in an inverted list index; a descriptor value was already present
during an insert operation.
Bytes 3 and 4 of the Additions 2 field contains the name of the descriptor that caused the
error.
The method of resolving the error varies, depending on whether you are using Adabas on
mainframe systems or Adabas on open systems.
Mainframe Systems
Open Systems
Complete the following steps:
Adabas Transaction Manager Messages and Codes