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

More documents

Recommendations

Info

ATM* - Adabas Transaction Manager Messages ATM078_10 EXTERNALLY-OWNED TRANSACTION INCOMPLETE. DB/TC: ddddd/cccc Explanation A database is trying to shut down in response to an ADAEND command; the ATM transaction manager has been asked to quiesce any transactions that involve the database, but has been unable to complete the process because at least one of those incomplete transactions is under the control of an external transaction coordinator. The database will not shut down until all global transactions are completed or backed out. The message identifies the database that is being shut down (value “ddddd”) and the external transaction coordinator (value “cccc”). Action ATM080_08 Use the facilities of the external transaction coordinator to force the completion or removal of the incomplete transactions. The transactions can be identified by the Online Services application. ‘STOP ALL USERS’ REQUESTED BY USER userid Explanation An Online Services user issued a "stop all transactions" request. “Userid” is the last 8 bytes of the user’s Communication ID. Action ATM081_08 This message is for information and audit purposes only. ‘FORCE STOP ALL USERS’ REQUESTED BY USER userid Explanation An Online Services user issued a "force stop all transactions" request. “Userid” is the last 8 bytes of the client session’s Communication ID. Action ATM082_08 This message is for information and audit purposes only. SELECTIVE MASS STOP USERS REQUESTED BY USER userid Explanation An Online Services user issued a selective mass “stop transactions” request. “Userid” is the last 8 bytes of the user’s Communication ID. Action ATM083_08 This message is for information and audit purposes only. FORCED SELECTIVE MASS STOP USERS REQUESTED BY USER userid Explanation An Online Services user issued a "forced selective mass stop transactions" request. “Userid” is the last 8 bytes of the user’s Communication ID. Action ATM084_10 This message is for information and audit purposes only. TRANSACTION BRANCH FORCIBLY COMPLETED. COMMID: commid Explanation In response to a "forced stop transactions" request from an Online Services user, ATM forced completion of the local branch of the transaction belonging to the client whose ID appears in the following ATM087 message. If the transaction had previously been prepared, ATM committed the branch; otherwise, ATM backed out the branch. Action 18 This message is for information and audit purposes only. Adabas Transaction Manager Messages and Codes
ATM085_10 TRANSACTION DETAILS TRANSFERRED TO JOURNAL. COMMID: commid Explanation In response to a "forced stop transactions" request from an Online Services user, the ATM transaction manager purged the transaction (branch) belonging to the client whose ID appears in the following ATM087 message. Details of the transaction (branch) can be found in the ATM suspect transaction journal file. Action ATM086_10 This message is for information and audit purposes only. RECOVERY RECORD DELETED FOR COMMID: commid Explanation In response to a request from an Online Services user, the ATM transaction manager purged from its recovery file, recovery information relating to the client whose ID appears in the following ATM087 message. Action ATM087_10 This message is for information and audit purposes only. commid Explanation This message relates to the message(s) immediately preceding it, and gives the 28-byte Communication ID (commID) of the client session associated with the earlier message(s). Action ATM088_10 Refer to the explanation of preceding message(s). ERROR TRANSFERRING TO STJ Explanation This message might be issued during forced restart of an ATM transaction manager, and indicates that a transaction that could not be completed could not be moved to the suspect transaction journal file. Subsequent messages provide more details of the error. Action ATM089_10 Refer to explanation of following message(s). DATA TRANSFERRED TO STJ FOR USER userid Explanation This message might be issued during forced restart of an ATM transaction manager, and indicates that a transaction that could not be completed has been moved to the suspect transaction journal file. “Userid” is the Client ID of the transaction’s owner. Action ATM090_04 This message is for information and audit purposes only. FORCED PRR DELETION REQUESTED BY USER userid Explanation The specified user forcibly deleted a recovery record from the ATM transaction manager's recovery file using the Online Services application. “userid” is the last 8 bytes of the user’s Communication ID. Action The message is for information and audit purposes only. Adabas Transaction Manager Messages and Codes ATM* - Adabas Transaction Manager Messages 19
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: ATM073_10 DB ACTIVITY NOT QUIESCED.
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 72 and 73:
Adabas Response Codes Response 26 O
Page 74 and 75:
Page 76 and 77:
Adabas Response Codes 72 Subcode Me
Page 78 and 79:
Adabas Response Codes Action Respon
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 ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?