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

Action
Response 114
Origin
Explanation
■ A read or update command tried to access a multiclient file's record using either a blank
or incorrect-length owner ID, or an owner ID that does not apply to the record.
■ An RI command was issued for a record that has been updated earlier in the same
transaction. The record cannot be released from hold status prior to transaction end. On
mainframe systems, subcode 5 is issued for this reason.
■ Subcode 19 is given when a base file record is not found in the address converter (AC). At
the end of a LOB update in the LOBfile, the associated base file record no longer existed.
■ Subcode 249 is given only when Adabas Vista is in use. Refer to the Adabas Vista
documentation for more information.
Open Systems
On open systems, the following subcodes may occur:
Subcode
249 (0x00F9)
Meaning
An invalid ISN was detected by Adabas Vista (open systems). The ISN specified
for an E1, HI or L1 command is not consistent with the definitions for the
partitioned file.
Action: Review the program logic
Correct the ISN problem and try again.
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
A refresh file error occurred. One of the following subcodes may be present:
Subcode Description
1
2
3
4
Adabas Transaction Manager Messages and Codes
A file refresh is not permitted for the file (PGMREFRESH=NO) or the command
ID field (ACBCID or ACBXCID) is not all blanks.
The user has not completed transactions to the file. Updates have been performed
or records are still in hold, but the user has not issued an ET or BT command to
commit or back out the updates.
Other users are accessing or updating the file. This is determined by the user access
or update counts available internally to Adabas.
The file is a multiclient file and the user is not a superuser.
Adabas Response Codes
113