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

More documents

Recommendations

Info

Adabas Response Codes 54 Subcode Meaning 75 76 77 78 79 80 81 This subcode is issued by Adabas Transaction Manager. Either a commit operation involving an external transaction coordinator failed, or resynchronization with an external transaction coordinator caused the transaction to be backed out. In the first case, ATM attempted to back out the transaction. For the first case, check the external transaction coordinator for the reason. Check for error messages from ATM transaction managers or the ATM client proxy of the failing job. This subcode is issued by Adabas Transaction Manager. An error occurred while an ATM transaction manager was attempting to rebuild the transaction hierarchy of a client session that has migrated from another ATM transaction manager’s domain as a result of dynamic transaction routing. ATM attempted to back out the transaction. Check the status of the transaction using Online Services. Check for error messages from ATM transaction manager or the ATM client proxy of the failing user. This subcode is issued by Adabas Transaction Manager. This message indicates that the client session had an open transaction and has been migrated from one node to another within a cluster (Sysplex), but ATM could not handle the transaction safely because no Migrated Transaction Record (MTR) file had been defined. The transaction was therefore backed out. Define and create an MTR file, and restart the ATM transaction managers and clustered application environments in the COR group. This subcode is issued by Adabas Transaction Manager. It was not possible to commit the client session’s transaction because of a pending ET syncpoint on a target database. This could be because of a concurrent online save operation, database termination, or a SYNCC operator command. Backout of the incomplete transaction was attempted. Restart the transaction when the pending ET syncpoint has been completed. Used by Adabas System Coordinator to signal the (optional) terminal timeout. Refer to the description of Generate RSP009/79 in the Adabas System Coordinator Parameters documentation for more information. This subcode is issued by Adabas Transaction Manager. The client session was not at ET status in the target database. Backout of the incomplete transaction was attempted. Restart the transaction. This subcode is issued by Adabas Transaction Manager. A memory shortage in the ATM transaction manager's address space caused the current global transaction to be backed out. Adabas Transaction Manager Messages and Codes
Subcode Meaning 82 83 84 85 86 90 91 Increase the amount of memory available to the ATM transaction manager, restart it, then restart the transaction. This subcode is issued by Adabas Transaction Manager. A memory shortage occurred in the ATM transaction manager's address space, and ATM attempted to back out the current global transaction. Increase the amount of memory available to the ATM transaction manager, restart it, then restart the transaction. This subcode is issued by Adabas Transaction Manager. An error occurred during a commit or backout operation for a global transaction. ATM attempted to back the transaction out. If the cause of the error is not apparent from console messages, contact your Software AG technical support representative. This subcode is issued by Adabas Transaction Manager. ATM reported conflicting use of an ETID. For an RE command, this subcode can be returned if the client is known to ATM but has no ETID. The client should issue a CL command to each open database; then re-open. This subcode is issued by Adabas Transaction Manager. The global transaction time limit (TMGTT) has been exceeded, and an attempt has been made to back out the global transaction. Correct the cause of the timeout, then restart the transaction. This subcode is issued by Adabas Transaction Manager. The global transaction time limit (TMGTT) has been exceeded, and the global transaction has been backed out. Correct the cause of the timeout, then restart the transaction. This subcode is issued by Adabas Transaction Manager. The ATM client proxy detected either an inconsistency between its view of the client session’s status and the ATM transaction manager’s view, or that the transaction manager had restarted. It attempted to back out on all target databases. Close the client’s sessions and start them again. This subcode is issued by Adabas Transaction Manager. Transactions on a target database were being quiesced, or an administrator issued a "stop" request for the session's transaction via ATM Online Services or operator command, or there was a pending ET syncpoint on the database. Backout of the incomplete transaction was attempted. Adabas Transaction Manager Messages and Codes Adabas Response Codes 55
Page 1 and 2:
Adabas Transaction Manager Adabas T
Page 3:
Table of Contents 1 Adabas Transact
Page 7 and 8: 2 Message Format and Severity Codes
Page 9 and 10: 3 ATM* - Adabas Transaction Manager
Page 11 and 12: ATM015_10 RRMS LOGNAME INCONSISTENC
Page 13 and 14: ATM028_10 DB RESTART. MAX TARGETS E
Page 15 and 16: ATM039_04 TRANSACTION RESTART NOT P
Page 17 and 18: ATM050_20 ‘SIGN-OFF’ FAILED, RE
Page 19 and 20: ATM061_10 MIXED TRANSACTION STATUS
Page 21 and 22: ATM073_10 DB ACTIVITY NOT QUIESCED.
Page 23 and 24: ATM085_10 TRANSACTION DETAILS TRANS
Page 25 and 26: ATM103_08 TM END PENDING, INCOMPLET
Page 27 and 28: ATM124_04 the details to your Softw
Page 29 and 30: ATM132_10 RMI RESYNC ERROR. SYS/CD/
Page 31 and 32: ATM141_04 DTP DISABLED FOR THIS JOB
Page 33 and 34: ATM172_10 TM tmid DID NOT COMPLETE
Page 35 and 36: 4 Adabas Transaction Manager Error
Page 37 and 38: error 076 Explanation Transaction (
Page 39 and 40: error 156 Explanation Client is alr
Page 41 and 42: error 236 Explanation A CICS/RMI sy
Page 43 and 44: error 316 Explanation Invalid dynam
Page 45 and 46: error 396 Explanation Attempt to ch
Page 47 and 48: error 480 Explanation A request fro
Page 49: error 540 Explanation The “F” c
Page 52 and 53: Adabas Response Codes Response 1 Or
Page 54 and 55: Adabas Response Codes Response 3 Or
Page 56 and 57: Adabas Response Codes 52 Subcode Me
Page 62 and 63: Adabas Response Codes Action 58 ■
Page 64 and 65: Adabas Response Codes 60 Subcode 6
Page 66 and 67: Adabas Response Codes Response 19 O
Page 70 and 71: Adabas Response Codes Action Respon
Page 92 and 93: Adabas Response Codes Action 88 ■
Page 96 and 97: Adabas Response Codes Action 92 Ope
Page 108 and 109:
Adabas Response Codes Response 94 O
Page 110 and 111:
Adabas Response Codes 106 Subcode M
Page 112 and 113:
Page 114 and 115:
Adabas Response Codes 110 Subcode 1
Page 116 and 117:
Adabas Response Codes Response 102
Page 118 and 119:
Adabas Response Codes Action Respon
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Adabas Response Codes Action 128 Su
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Adabas Response Codes 134 Subcode O
Page 140 and 141:
Adabas Response Codes 136 Subcode O
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
188
Page 194 and 195:
User Abend Codes Code Module 27 28
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
200
Page 206:
202
show all

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

Create successful ePaper yourself

Delete template?

Save as template?