Version 8.2.1
 —  Adabas Transaction Manager Messages and Codes  —

Adabas Transaction Manager Error Codes

Although many of the following error codes are handled internally, some may appear in console messages or in the Additions 2 field of Adabas control blocks. If the required action is not clear from the explanations of the console messages or error codes, contact your Software AG technical support representative for advice.

Overview of Messages

error 012 | error 016 | error 020 | error 024 | error 028 | error 032 | error 036 | error 044 | error 048 | error 052 | error 056 | error 060 | error 064 | error 068 | error 072 | error 076 | error 080 | error 084 | error 086 | error 088 | error 092 | error 096 | error 104 | error 108 | error 112 | error 116 | error 120 | error 124 | error 128 | error 132 | error 136 | error 140 | error 144 | error 148 | error 152 | error 156 | error 160 | error 164 | error 168 | error 172 | error 176 | error 180 | error 184 | error 188 | error 192 | error 196 | error 200 | error 204 | error 208 | error 212 | error 216 | error 220 | error 224 | error 228 | error 232 | error 236 | error 240 | error 244 | error 248 | error 252 | error 256 | error 260 | error 264 | error 268 | error 272 | error 276 | error 280 | error 284 | error 288 | error 292 | error 296 | error 300 | error 304 | error 308 | error 312 | error 316 | error 320 | error 324 | error 328 | error 332 | error 336 | error 340 | error 344 | error 348 | error 352 | error 356 | error 360 | error 364 | error 368 | error 372 | error 376 | error 380 | error 384 | error 388 | error 392 | error 396 | error 400 | error 404 | error 408 | error 412 | error 416 | error 420 | error 424 | error 428 | error 432 | error 436 | error 440 | error 444 | error 448 | error 452 | error 456 | error 460 | error 468 | error 472 | error 476 | error 480 | error 484 | error 488 | error 492 | error 496 | error 500 | error 504 | error 508 | error 512 | error 513 | error 514 | error 515 | error 516 | error 517 | error 520 | error 524 | error 528 | error 536 | error 540 | error 544 | error 588

error 012
Explanation

Status conflict - transaction is in prepare phase.


error 016
Explanation

Status conflict - transaction is in backout phase .


error 020
Explanation

Queue management error - item not found.


error 024
Explanation

Invalid service call.


error 028
Explanation

Insufficient memory for a new global transaction queue entry.


error 032
Explanation

Insufficient memory for a new entry in the target database list.


error 036
Explanation

Attempt to add a duplicate global transaction queue element.


error 044
Explanation

Invalid global transaction queue element address.


error 048
Explanation

Syncpoint request did not come from CICS RMI.


error 052
Explanation

Status conflict - target is in prepare phase.


error 056
Explanation

Status conflict - target is in backout phase.


error 060
Explanation

Queue management error.


error 064
Explanation

Unexpected Adabas response code.


error 068
Explanation

No target was updated.


error 072
Explanation

No transaction is open.


error 076
Explanation

Transaction (branch) backed out.


error 080
Explanation

Transaction (branch) partially backed out.


error 084
Explanation

Local or remote ATM transaction manager not available.


error 086
Explanation

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


error 088
Explanation

The ATM transaction manager did not receive the request.


error 092
Explanation

Target not prepared.


error 096
Explanation

Incorrect positioning data in service call.


error 104
Explanation

Invalid service call type.


error 108
Explanation

ETID missing or invalid.


error 112
Explanation

Function not implemented.


error 116
Explanation

More than one target DB record found.


error 120
Explanation

Transactions on the target database are being quiesced.


error 124
Explanation

Transactions on the target database were not fully quiesced.


error 128
Explanation

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


error 132
Explanation

Transaction status conflict.


error 136
Explanation

Unable to complete existing transaction.


error 140
Explanation

ATM session number mismatch during RMI synchronization.


error 144
Explanation

Handshake information buffer overflow.


error 148
Explanation

ATM restart processing aborted by operator.


error 152
Explanation

Error reading ET data.


error 156
Explanation

Client is already active.


error 160
Explanation

Insufficient memory for a new Adabas buffer area.


error 164
Explanation

All required target databases and ATMs are unavailable.


error 168
Explanation

Duplicate transaction coordinator record in PRR file.


error 172
Explanation

Transaction (branch) not prepared.


error 176
Explanation

Invalid status for NONDTP override.


error 180
Explanation

Committed, outcome pending.


error 184
Explanation

Transaction is in commit phase.


error 188
Explanation

A target database is not signed on for distributed transaction processing.


error 192
Explanation

A target is in commit phase.


error 196
Explanation

Client proxy parameter error in V1 call forwarding.


error 200
Explanation

Syncpoint request did not come from RRS.


error 204
Explanation

Non-zero response set in ACB.


error 208
Explanation

Handshake collision between two ATM transaction managers.


error 212
Explanation

Partner ATM failed to prepare.


error 216
Explanation

Partner ATM failed to commit.


error 220
Explanation

Partner ATM failed to back out.


error 224
Explanation

Mixed transaction completion.


error 228
Explanation

An RRMS error occurred.


error 232
Explanation

RRMS gave an invalid exit number.


error 236
Explanation

A CICS/RMI syncpoint operation failed.


error 240
Explanation

The RMI is not enabled.


error 244
Explanation

Command type invalid for wrapping.


error 248
Explanation

Client ID already exists in the global transaction queue.


error 252
Explanation

No free DRQ slots - TMDRQ parameter is too small.


error 256
Explanation

Command not handled - send to local ATM transaction manager.


error 260
Explanation

A CICS command issued by the synchronization manager failed.


error 264
Explanation

TRUE work area is not valid.


error 268
Explanation

TRUE has not fully initialized.


error 272
Explanation

A local database returned response code 148 (ADARSP148).


error 276
Explanation

Mode override not valid in session’s current status.


error 280
Explanation

A session attempted to use more than 191 databases at once.


error 284
Explanation

Incomplete handshake information element.


error 288
Explanation

The transaction manager is running in “local only “ mode (TMNODES=0).


error 292
Explanation

Database ID already in the target list.


error 296
Explanation

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


error 300
Explanation

The partner ATM node table is full - inadequate TMNODES parameter.


error 304
Explanation

Insufficient memory.


error 308
Explanation

No dynamic Client IDs available - TMDYNTCIDS parameter is too small.


error 312
Explanation

Adabas buffer area too small.


error 316
Explanation

Invalid dynamic Client ID detected.


error 320
Explanation

Command not valid - transaction branch open.


error 324
Explanation

Client not known to local ATM transaction manager.


error 328
Explanation

Client not known to partner ATM transaction manager.


error 332
Explanation

Conflicting activity for transaction.


error 336
Explanation

Request should be sent to root ATM transaction manager.


error 340
Explanation

A session attempted to use more than 191 ATM transaction managers in the same transaction.


error 344
Explanation

‘Forget branch’ failed.


error 348
Explanation

Transaction ID conflict.


error 352
Explanation

Record buffer too small.


error 356
Explanation

Maximum number of open databases exceeded. Increase the appropriate client runtime control.


error 360
Explanation

Transaction has been committed.


error 364
Explanation

Transaction has been prepared.


error 368
Explanation

Unsolicited syncpoint not allowed.


error 372
Explanation

Bad return code from ADASVC.


error 376
Explanation

Invalid Database ID.


error 380
Explanation

A CICS command failed during an RMI syncpoint operation.


error 384
Explanation

XID mismatch was detected during an RMI syncpoint operation.


error 388
Explanation

RMI reported “should not be in doubt”.


error 392
Explanation

RMI reported the transaction “lost to cold start”.


error 396
Explanation

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


error 400
Explanation

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


error 404
Explanation

A DTP=ET database failed to commit.


error 408
Explanation

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


error 412
Explanation

Version mismatch; use ATM components of same version everywhere.


error 416
Explanation

RQE overflow; DB list truncated.


error 420
Explanation

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


error 424
Explanation

Invalid request for Unsolicited Syncpoint Participant status.


error 428
Explanation

DB has conflicting local/remote information.


error 432
Explanation

Null Communications ID detected.


error 436
Explanation

Multiple ET data records detected.


error 440
Explanation

Multiple migrated transaction records were found.


error 444
Explanation

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


error 448
Explanation

The Client-sideTransactionManager option was specified, but the CICS RMI components have not been configured correctly.


error 452
Explanation

An unexpected return code was given by a SYSCO daemon .


error 456
Explanation

An unexpected and unnecessary call was received from a SYSCO daemon .


error 460
Explanation

An error occurred during the client proxy's check for DTP=RM. .


error 468
Explanation

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


error 472
Explanation

An unexpected condition was returned by the Adabas System Coordinator’s router interface. .


error 476
Explanation

During a sequence of ET commands, the first of which supplied ET data, ET data was supplied on a session that used a different ETID. .


error 480
Explanation

A request from the CICS RMI attempted to act on a transaction that was not owned by the CICS RMI. .


error 484
Explanation

An ATM transaction manager detected an invalid service call to itself. .


error 488
Explanation

An invalid communication-ID was supplied. .


error 492
Explanation

An invalid communication-ID was detected in the transaction manager's queue. .


error 496
Explanation

The application did not back out everywhere after a response code 9 (ADARSP009), or the application terminated a transaction but did not issue ET or BT to all affected databases.


error 500
Explanation

There was a duplicate attempt to sign a DTP=RM database on to a Transaction Manager for Distributed Transaction Processing.


error 504
Explanation

There was an attempt to sign a DTP=RM database on to a remote Transaction Manager for Distributed Transaction Processing.


error 508
Explanation

There was an invalid attempt to remove a database from a global transaction.


error 512
Explanation

Transaction status is not known because a status-check request to the local TM returned a bad response code. .


error 513
Explanation

Transaction status is not known because a status-check request to the local TM returned error 88. .


error 514
Explanation

Transaction status is not known because a status-check request to the local TM returned error 412.


error 515
Explanation

Transaction status is not known because a status-check request to the local TM returned error 488.


error 516
Explanation

Transaction status is not known because a status-check request to the local TM returned error 60.


error 517
Explanation

Transaction status is not known because an Adabas buffer area could not be acquired for a status-check operation. .


error 520
Explanation

In a DTR environment, a client session has migrated to another system, but no MTR file is in use. .


error 524
Explanation

A session could not be switched to serial ET/BT mode, because the local TM was already involved in the current transaction. .


error 528
Explanation

The client proxy failed to provide a return code for a CICS RMI syncpoint operation. .


error 536
Explanation

An unknown TM node ID was detected while processing DTR migration. .


error 540
Explanation

The “F” command option on a BT command could not be honored, because a distributed transaction was in process. .


error 544
Explanation

The client session tried to change a database that’s executing outside the scope of the client session’s System Coordinator group, but this is disallowed by the Coordinate Adabas DBs Outside the Group runtime control. .


error 588
Explanation

A conflict with shared hold status option "H" has been detected. The client session is using this option in a conflicting manner during an ET or BT sequence after a two-phase commit process has been performed. The transaction outcome is unaffected but records may no longer be in shared hold status. The use of this option should be reviewed. .


Top of page