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

More documents

Recommendations

Info

ATM* - Adabas Transaction Manager Messages ATM005_20 Error reading TM controls; RSP/SUB: {rsp/sub} Explanation An unexpected response code was encountered during reading of the TM controls from the configuration file. Action ATM007_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. COR GROUP ALREADY HAS MANAGER: manager Explanation The ATM manager indicated in the message is already active locally in the local COR group. It is not possible to have more than one ATM transaction manager associated with the same COR group and executing in the same location (that is, under the same Adabas ID table, or Adabas SVC). Action ATM010_20 Do not attempt to run more than one ATM transaction manager under the same ID table and associated with the same COR group. GENERAL GETMAIN FAILED Explanation ATM was unable to acquire enough storage to initialize. Action ATM012_20 Increase the amount of memory available to the job and restart it. UNABLE TO ACQUIRE STORAGE FOR area-name Explanation ATM was unable to acquire enough storage for the area named. Action ATM013_20 Increase the amount of memory available to the job and restart it. INITIALIZATION ERROR. FUNCTION/RF: function/rf Explanation An error occurred during the initialization of an interface to an external transaction coordinator. Action ATM014_20 Check the documentation for the external transaction coordinator being used 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 “function” and “rf”. RRMS LOGNAME CHECK FAILED Explanation This message relates to the initialization of the ATM interface with RRMS. The ATM node ID has changed since ATM was last used with this RRMS system. Action 6 The node ID of the Adabas System Coordinator daemon within which the ATM transaction manager is running as a service must not be changed while there are global transactions in progress. If you have changed the Node ID and are sure that there were no incomplete global transactions, you can override this initialization error using the parameter TMRESTART=FORCE. Adabas Transaction Manager Messages and Codes
ATM015_10 RRMS LOGNAME INCONSISTENCY OVERRIDDEN Explanation This message relates to the initialization of the ATM interface with RRMS. The node ID of the Adabas System Coordinator daemon within which the ATM transaction manager is running as a service has changed since ATM was last used with this RRMS system. However, the inconsistency was ignored because of the setting of the parameter TMRESTART. Action ATM016_20 None. This message is for information only. RRMS HAS LOST HARDENED RESTART DATA Explanation This message relates to the initialization of the ATM interface with RRMS. Because RRMS has lost some restart data, integrity cannot be guaranteed for incomplete transactions that were under the control of RRMS. Action ATM017_20 If it is not possible to recover the RRMS restart data, you can use the parameter TMRESTART to force the ATM transaction manager to initialize. Details of any incomplete transactions are then transferred to the STJ file and can be examined using the SYSATM application. FAILED TO OPEN ATMLOG. RC/RF:rc/rf Explanation The ATM transaction manager was unable to open the ATMLOG1 or ATMLOG2 dataset. Action ATM018_20 Check the definition of the ATMLOG1/2 datasets. If the cause of the error is not apparent, report the problem to your Software AG support representative, noting the values of “rc” and “rf”. Unexpected behavior for node dbid Explanation The node (dbid) is expected to be an Adabas System Coordinator daemon within which an ATM transaction manager is running as a service, but its behavior is not consistent with this. Action ATM019_20 Check the indicated node. RRS IS NOT ACTIVE; ATM WILL WAIT AND RETRY Explanation This message relates to the initialization of the ATM interface with RRMS. Initialization cannot complete because the RRS component of RRMS is not available. Action ATM020_04 Report the problem to your systems programming staff. The ATM transaction manager cannot initialize until RRS is active again. RRS EXITS HAVE BEEN SET Explanation If the ATM transaction manager is started with the parameter TMSYNCMGR=RRMS, this message is issued when the ATM RRMS interface has been initialized. Adabas Transaction Manager Messages and Codes ATM* - Adabas Transaction Manager Messages 7
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: 3 ATM* - Adabas Transaction Manager
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 58 and 59: Adabas Response Codes 54 Subcode Me
Page 60 and 61:
Adabas Response Codes 56 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:
Page 70 and 71:
Adabas Response Codes Action Respon
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
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:
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?