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

Adabas Response Codes
Response 186
Origin
Explanation
Action
Response 196
Origin
Mainframe systems only
A wrong cipher code has been specified or a compressed data record is bad (does not conform
to the Field Description Table).
The leftmost two bytes of the ACB's Additions 2 field or the ACBX's Error Subcode
(ACBXERRC) field contain the field or descriptor name where the error was detected. The
rightmost two bytes of the same ACB or ACBX field contain an internal code identifying
the routine that detected the error.
If the file that was accessed when this response code occurred is ciphered, check whether
the correct cipher code has been specified. Correct the cipher code, if necessary.
If the error is not due to an incorrect cipher code, run the ADACMP DECOMPRESS INFILE
utility function to unload and decompress all records of the file. ADACMP will write records
where it detects errors to its error dataset (DD/FEHL). Contact your Software AG technical
support representative for assistance.
Open systems only
Explanation Referential integrity has been violated. Bytes 3 and 4 of the Additions 2 field contain the name
of the violated constraint. Bytes 1 and 2 of the Additions 2 field contain the reason as a two-byte
binary number:
Action
Response 197
Origin
Explanation
Action
148
Subcode Meaning
1
3
5
7
8
Required ISN in hold by another user
Maximum number of ISNs held by one user is reached
Check integrity mismatch, required value not found during check
Double update to a record within a cascade detected
Limit of stacked commands reached
Handle the referential integrity violation, for example, write an error message.
Mainframe systems only
The DEUQ pool is too small.
Increase the ADARUN LDEUQP parameter.
Adabas Transaction Manager Messages and Codes