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

Response 9
Origin
Mainframe and open systems
Explanation The meaning of this response code varies, depending on whether you are using Adabas on
mainframe systems or Adabas on open systems.
Mainframe Systems
A subcode indicating the specific cause and action for this response code appears in the
low-order (rightmost) two bytes of the ACB's Additions 2 field or in the ACBX's Error Subcode
(ACBXERRC) field. The following are the subcodes and their meanings:
Subcode Meaning
1
2
3
15
The user was backed out because the hold queue was full
Action: Set the number of hold queue elements (ADARUN NH parameter) higher,
or tune the application to issue more frequent ET commands.
The transaction time limit (TT) has been exceeded, and the transaction was backed
out.
Action: Correct the cause of the timeout, then restart the transaction.
One of the following is the case:
■ The transaction non-activity time limit (TNAE, TNAX, or TNAA) has been
exceeded.
■ The user was stopped by the STOPF or STOPI operator, or an Adabas Online
System command.
■ A security violation response code has been returned for an ET-logic user.
Information about response codes for security violations is provided in the Adabas
Security documentation.
■ When a new user issues an OP cmd with the same user ID (in ADD1) as an earlier
user did and the earlier user was inactive for more than 60 seconds, the new user
can, by issuing a second OP cmd again (the first OP cmd will get response code
9, subcode 64), take over the user ID of the earlier user. When the earlier user
becomes active again, this subcode can be received.
Action: Correct the cause of the timeout, then restart the transaction.
The user was backed out because a pending Work area overflow occurred during
this operation.
Action: Either reduce the transaction length to lessen the data protection area
requirement, or increase the protection area on Work.
Adabas Transaction Manager Messages and Codes
Adabas Response Codes
51