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

More documents

Recommendations

Info

ATM* - Adabas Transaction Manager Messages ATM045_04 TRANS/BRANCHES PENDING AFTER RESTART: count Explanation This message is issued by an ATM transaction manager at the end of restart processing. It indicates the number of incomplete transactions or transaction branches that could not be completed or backed out during ATM restart processing, and so remain incomplete. These transactions remain incomplete until they can be completed or fully backed out. Action ATM046_04 Note: This message is issued before the transaction manager attempts to resynchronize incomplete transactions that are controlled by the CICS syncpoint manager or by RRS. This message is for information only. TRANS/BRANCHES TRANSFERRED TO STJ: count Explanation This message is issued by an ATM transaction manager at the end of restart processing. It indicates the number of incomplete transactions or transaction branches that could not be completed or backed out during the daemon recovery restart processing, and that were removed and recorded in the suspect transaction journal file in the transaction manager's recovery file. The number indicated should be zero unless the TMRESTART parameter indicates a forced restart. Action ATM047_20 This message is for information only. ATM INITIALIZATION FAILED, error description Explanation A serious error prevented the transaction manager from initializing. Where possible an error description is provided to identify the cause of the error, otherwise “RC/RF” error codes are displayed. Action ATM048_08 If the reason for the failure is not clear please contact your Software AG support representative. INITIALIZED, Vvers, SESSION sess Explanation This message marks the successful completion of an ATM transaction manager's initialization processing. The version, release, and maintenance level of ATM are displayed, followed by the session number (sess) for this execution of the transaction manager. Action ATM049_04 This message is for information only. ERRORS READING RECOVERY RECORDS: count Explanation This message appears at the end of the transaction manager's initialization processing if any errors were encountered reading recovery records. Action 12 The message is for information only. For information about the errors encountered, refer to the error messages that precede this message. Adabas Transaction Manager Messages and Codes
ATM050_20 ‘SIGN-OFF’ FAILED, RESPONSE CODE {rsp} Explanation This message can appear during the closedown process of a nucleus that was running with DTP=RM. It indicates that the nucleus called the local ATM transaction manager to notify it of the closedown, but the command failed with response code rsp. Action ATM051_20 Nucleus termination will continue. Any incomplete global transactions will be resynchronized when the nucleus next communicates with the ATM transaction manager. ‘SIGN-OFF’ FAILED, ERROR CODE error-code Explanation This message can appear during the closedown process of a nucleus that was running with DTP=RM. It indicates that the nucleus called the local ATM transaction manager to notify it of the closedown, but ATM returned the error code “error-code”. Action ATM052_20 Check the meaning of the given error code, to see if ATM needs any corrective action. Nucleus termination will continue. Any incomplete global transactions will be resynchronized when the nucleus next communicates with the transaction manager. PROTOCOL ERROR. ATM NOT INITIALIZED. Explanation This message is issued if an ATM transaction manager receives an operator command before it has completed its initialization processing. Action ATM054_20 Wait, and re-issue the command later. HANDSHAKE ERROR; ID/RSP/SUB/CMD: dbid/rsp/sub/cmd Explanation An error occurred while the transaction manager was trying to handshake with the partner transaction manager identified by “dbid”. The error was an unexpected Adabas response code (rsp). The subcode (sub) and command code (cmd) are provided. Action ATM055_20 If the cause of the error is not clear from the description of the response code, report the details to your Software AG support representative, noting the values of the variables. HANDSHAKE ERROR; ERR/QERR: error-code/queue-error Explanation An error occurred while the transaction manager was attempting to handshake with a partner transaction manager. The error code and, if applicable, a queue management error are provided. Action Refer to the descriptions of the possible error codes. If the cause of the error is not apparent, report the details to your Software AG support representative, noting the error code. Adabas Transaction Manager Messages and Codes ATM* - Adabas Transaction Manager Messages 13
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: ATM039_04 TRANSACTION RESTART NOT P
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 68 and 69:
Adabas Response Codes 64 Subcode Me
Page 70 and 71:
Adabas Response Codes Action Respon
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Adabas Response Codes 72 Subcode Me
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Adabas Response Codes Action 88 ■
Page 94 and 95:
Page 96 and 97:
Adabas Response Codes Action 92 Ope
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
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:
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?