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

Adabas Response Codes
Response 3
Origin
Mainframe and open systems
Explanation One of the following has occurred:
Response 4
Origin
■ An end-of-file or end-of-list condition was detected.
■ A program tried to read/change a multiclient file's record using either a blank or
incorrect-length owner ID, or an owner ID that is not allowed for the record.
■ Subcode 4: End of LOB value reached. An attempt was made to read a LOB value segment
that begins after the end of the value. This response code/subcode is given to an L1/L4
command with Command Option 2 set to L if the ISN Lower Limit value is greater than or
equal to the length of the LOB value being read.
■ Subcode 249: Adabas Vista has determined that no data is available to satisfy this command
due to one of the following reasons:
■ A partitioned file end-of-file or end-of-list condition was detected.
■ None of the partitions were available/online and all of them have the file parameter
Critical set to NO.
No action is required.
Mainframe systems
Explanation The internal Adabas TRS storage directory is full.
Action
Response 7
Origin
Free some of the active queries.
Mainframe systems only
Explanation A complex search command was rejected because it was estimated that it would exceed the
maximum search time TLSCMD.
Response 8
Origin
Mainframe systems only
Explanation The current user's command was interrupted to prevent a Work overflow because of a pending
backout operation.
Action
50
The value specified for the LP parameter might have to be increased.
Adabas Transaction Manager Messages and Codes