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

Response 198
Origin
Explanation
Response 199
Origin
Explanation
Response 200
Origin
Explanation
Mainframe systems only
An attempt was made to duplicate a descriptor value for a unique descriptor. In an ACB,
the leftmost two bytes of the Additions 2 field may contain the descriptor name; in an ACBX,
the Error Character Field (ACBXERRB) may contain the descriptor name. The following
subcodes may accompany this response code:
Subcode Meaning
1
2
3
Unique descriptor insert failed; value already exists in the index.
Unique descriptor insert failed; value in use by another user on this nucleus.
Unique descriptor insert failed; value in use by another user on another cluster
nucleus.
Mainframe systems only
An inconsistency in the inverted list index was found during an update operation. 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. This response
code can also occur if UTYPE=EXU was specified for an ADARES BACKOUT operation that
uses the sequential (SIBA) log.
Mainframe and open systems
Either an invalid cipher code or an Adabas SAF Security or Adabas security violation was
detected.
The command could not satisfy the necessary security checks. This response code may be
accompanied by one of the following subcodes:
Subcode Meaning
0
1
2
3
4
5
6
7
1060
A standard user check failed.
There is no free user file cache entry for a workstation user.
A cross-level security check failed.
No security information is available for the command.
A timeout occurred during a workstation logon.
An internal SAF Kernel error occurred.
A failure occurred during a newcopy/restart operation. The nucleus terminates.
A request to make an ABS security check was not of the correct format.
Open systems ADASAF phase 1 failed.
Adabas Transaction Manager Messages and Codes
Adabas Response Codes
149