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

More documents

Recommendations

Info

ATM* - Adabas Transaction Manager Messages ATM069_10 TRANSACTIONS CANNOT BE QUIESCED. DB/ERR: dbid/err Explanation The indicated error occurred while the transaction manager was trying to quiesce transactions involving database “dbid”. As a result, ATM was unable to complete one or more transactions. Action ATM070_10 Refer to the descriptions of the possible error codes. If the appropriate action is not clear, contact your Software AG support representative. LOCAL TRAN(S) STILL IN DOUBT ON DB dbid Explanation ATM attempted to complete (commit or back out) all active global transactions that involve the indicated database, but at the end of the process, at least one transaction or transaction branch involving the database remained active. Action ATM071_10 This message may be preceded or followed by messages requiring action. If so, refer to the explanations of those messages. FOLLOWING TMS IN ERROR: id-list Explanation While the ATM transaction manager was attempting to quiesce transactions on a database, it asked one or more partner managers to do the same, but one or more of them returned an unexpected error. The message lists up to four partner transaction managers that failed to carry out its request. Action ATM072_10 Use Online Services to check the status of the indicated ATM nodes and, if necessary, to quiesce each transaction manager’s transactions for the required database. HEURISTIC TERMINATIONS MAY RESULT Explanation This message is preceded by message ATM068 and one or more of the messages ATM069, ATM070, and ATM071. Action 16 The database indicated in message ATM068 received an ADAEND command and asked ATM to quiesce its global transactions. At the end of the process, at least one transaction or transaction branch involving the database remained active. Any such transaction or transaction branch is heuristically terminated when its TT time limit expires, which could result in mixed completion of the related global transactions. This message warns of the impending loss of global transaction integrity for those global transactions that are still active. Use Online Services to identify the transactions that could not be quiesced. Any transaction that remains active when its TT time limit expires is heuristically committed. To prevent this, if appropriate, use Online Services to forcibly back out any such transaction. Adabas Transaction Manager Messages and Codes
ATM073_10 DB ACTIVITY NOT QUIESCED. CHECK ATM MANAGER nodeID Explanation A DTP=RM nucleus that received an ADAEND command requested the transaction manager with the indicated Node ID to quiesce its global transactions. The request failed. Action ATM074_10 Check that the indicated transaction manager is active, and check for error messages issued by it. Use Online Services to ask the transaction manager to quiesce transactions on the database. RRMS REPORTED ERROR. FNC/RF/COMMID: fnc/rf/comm-id Explanation A problem was encountered with a transaction that is (or should be) under the control of RRMS. The RRMS function in error and its return code (values “fnc” and “rf”) are provided, together with the 28-byte Communications ID of the user who owns the transaction. Action ATM075_10 Check the RRMS documentation to determine the meaning of the return code (value “rf”). If the cause of the problem is still not apparent, contact your Software AG support representative, noting the values of “fnc” and “rf”. RRMS REPORTED EXIT MANAGER UNAVAILABLE Explanation ATM is interfacing to RRMS and has been notified that one of the RRMS exit managers has become unavailable. ATM continues to interface to RRMS once the exit manager has restarted. Action ATM076_10 Report the problem to your systems programming staff. RRMS REPORTED EXITS UNSET. REASON: rrrr Explanation ATM is interfacing to RRMS and has been notified that its exits have become unavailable. Action ATM077_10 Check the console log for other messages that may indicate the cause of the problem. Check the RRMS documentation to determine the meaning of the reason code (value “rrrr”). If possible, correct the problem and restart ATM. If the cause of the problem is not apparent, contact your Software AG support representative, noting the value of “rrrr”. RRS EXIT FAILED. X: xx R: rr AB: aaaaaaaa ABR: nnnnnnnn Explanation ATM is interfacing to RRMS and an error has occurred in one of its exit routines. The message details the exit number (“xx”), failure reason (“rr”), ABEND code (“aaaaaaaa”) and reason code (“nnnnnnnn”). Action If the cause of the problem is not apparent from the details of the message, contact your Software AG support representative, noting all the values given in the message. Adabas Transaction Manager Messages and Codes ATM* - Adabas Transaction Manager Messages 17
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: ATM061_10 MIXED TRANSACTION STATUS
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 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:
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?