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

Adabas Response Codes
Response 144
Origin
Explanation
Action
Response
145
Origin
Mainframe and open systems
One of the following occurred:
■ The ISN specified with an update (A1) command was not in hold status for the user and
command option H was not specified.
■ An ET or BT command specifying the M (multifetch) option specified an ISN in the ISN
buffer that is not in hold status for the user. All currently held ISNs are released from hold
status.
In this case on open systems, the first 2 bytes of the Additions 2 field (in binary format)
contain the offset of that ISN in the ISN buffer.
Put the ISN in hold status before using the A1 command or the multifetch ET or BT
commands.
If Adabas Transaction Manager is in use, verify that the setting for the Transaction Model
parameter is appropriate for the program that was executing and is also appropriate for the
runtime environment in use.
Mainframe and open system
Explanation The exact meaning of this response code varies, depending on whether you are using Adabas
on mainframe systems or Adabas on open systems.
130
Mainframe Systems
On mainframe systems, one of the following situations occurred:
■ An N1/N2 command was issued, but no hold queue entry was available.
■ A command was issued with the return option specified that attempted to hold an ISN
already in the hold queue for another user. The command is not placed in wait status.
Use the subcode associated with this response code to further clarify why this response
occurred.
Subcode Meaning
0
1
2
8
N2 command for an existing ISN was issued.
Hold queue space problem detected. The user is the only active user and is running
with the -R option.
The ISN was held by someone else. The read request is running with the -R option.
The hold status of a record could not be upgraded from shared to exclusive because
another user was already waiting to do the same. The two users became deadlocked.
Adabas Transaction Manager Messages and Codes