Adabas Transaction Manager Error Codes

Status conflict - transaction is in prepare phase

Status conflict - transaction is in backout phase

Queue management error - item not found

Invalid service call

Insufficient memory for a new global user queue entry

Insufficient memory for a new entry in the target database list

Attempt to add a duplicate global user queue element

Insufficient memory for a new global user queue index entry

Invalid global user queue element address

Syncpoint request did not come from CICS RMI

Status conflict - target is in prepare phase

Status conflict - target is in backout phase

Queue management error

Unexpected Adabas response code

No target was updated

No transaction is open

Transaction (branch) backed out

Transaction (branch) partially backed out

Local or remote ATM daemon not available

Backout was attempted because the global transaction time limit was exceeded.

The ATM daemon did not receive the request

Target not prepared

Incorrect positioning data in service call

ETID already in use — new OP command required

Invalid service call type

ETID conflict

Function not implemented

More than one target DB record found

Transactions on the target database are being quiesced

Transactions on the target database were not fully quiesced

Heuristic completion (commit or back out) by either ATM or a DTP=RM database may have caused inconsistent ET data

Transaction status conflict

Unable to complete existing transaction

ATM session number mismatch during RMI synchronization

Handshake information buffer overflow

ATM restart processing aborted by operator

Error reading ET data

User is already active

Insufficient memory for a new Adabas buffer area

All required target databases and ATMs are unavailable

Duplicate transaction coordinator record in PRR file

Transaction (branch) not prepared

Invalid status for NONDTP override

Committed, outcome pending

Transaction is in commit phase

A target database is not signed on for distributed transaction processing

A target is in commit phase

Proxy parameter error in V1 call forwarding

Syncpoint request did not come from RRS

Non-zero response set in ACB

Handshake collision between two ATM daemons

Partner ATM failed to prepare

Partner ATM failed to commit

Partner ATM failed to back out

Mixed transaction completion

An RRMS error occurred

RRMS gave an invalid exit number

A CICS/RMI syncpoint operation failed

The RMI is not enabled

Command type invalid for wrapping

Client ID already exists in the global user queue

No free DRQ slots - TMDRQ parameter is too small

Command not handled - send to local ATM daemon

A CICS command issued by the synchronization manager failed

TRUE work area is not valid

TRUE has not fully initialized

A local database returned response 148

Mode override not valid in user’s current status

A user attempted to use more than 191 databases at once

Incomplete handshake information element

The ATM daemon is running in “local only “ mode (TMNODES=0)

Database ID already in the target list

The target DB list index is full - TMTARGETSG parameter is too small

The partner ATM node table is full - inadequate TMNODES parameter

Insufficient memory

No dynamic Client IDs available - TMDYNTCIDS parameter is too small

Adabas buffer area too small

Invalid dynamic Client ID detected

Command not valid - transaction branch open

User not known to local ATM daemon

User not known to partner ATM daemon

Conflicting activity for transaction

Request should be sent to root ATM daemon

A user attempted to use more than 191 ATM daemons in the same transaction

‘Forget branch’ failed

Transaction ID conflict

Record buffer too small

Maximum number of open databases exceeded. Increase the appropriate job parameter.

Transaction has been committed

Transaction has been prepared

Unsolicited syncpoint not allowed

Bad return code from ADASVC

Invalid Database ID

A CICS command failed during an RMI syncpoint operation

XID mismatch was detected during an RMI syncpoint operation

RMI reported “should not be in doubt”

RMI reported the transaction “lost to cold start”

Attempt to change two DTP=ET databases in a single transaction

Transaction’s status on a DTP=ET database is not known

A DTP=ET database failed to commit

A DTP=ET database cannot be changed by a transaction that is controlled by an external coordinator

Version mismatch; use ATM components of same version everywhere

RQE overflow; DB list truncated

An IMS/TM ROLLBACK function failed; reason code in Additions-2

Invalid request for Unsolicited Syncpoint Participant status

DB has conflicting local/remote information

Null Communications ID detected

Multiple ET data records detected

Multiple migrated transaction records were found

The RRMS stubs have not been linked to ATMKRN in the application environment

The parameter setting LCLSYNC=YES was specified, but the CICS RMI components have not been configured correctly

An unexpected return code was given by a SYSCO daemon

An unexpected and unnecessary call was received from a SYSCO daemon

Response 9 occurred during the client proxy’s check for DTP=RM

An invalid ISN was given for a Persistent Error record.

There is a non-zero response code pending for the session.

An ATM transaction manager detected an invalid service call to its own database.