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

More documents

Recommendations

Info

Adabas Response Codes 52 Subcode Meaning 17 18 19 20 21 22 23 24 25 At the end of an online recovery process that was initiated after the failure of a peer nucleus in an Adabas cluster, the nucleus was unable to reacquire the ETID specified by the user in the Additions 1 field of the OP command. Action: (In the application program:) Redo the OP command with the ETID specified in the Additions 1 field to reacquire the user ID. Contact your Software AG technical support representative. The user's active transaction was interrupted and backed out because a peer nucleus in an Adabas cluster terminated abnormally. Action: (In the application program:) Rerun the transaction. The user's active command was interrupted and stopped because a peer nucleus in an Adabas cluster terminated abnormally. If the interrupted command was using a command ID (CID), the command ID is deleted. Action: (In the application program:) Clean up and reacquire the current context pertaining to Adabas command IDs; rerun the transaction. The Adabas cluster nucleus assigned to the user terminated while the user had an open transaction. The transaction has been or will be backed out. Action: (In the application program:) If the user was defined with a user ID (ETID) in the Additions 1 field of the OP command, redo the OP command to reacquire the ETID; clean up and reacquire the current context pertaining to Adabas command IDs; rerun the transaction. The user's active command was waiting for an ISN in hold status when the user was backed out and closed due to a timeout or a STOP command. The user's active command was waiting for free space in the work pool when the user was backed out and closed due to a timeout or a STOP command. The user's command was routed to a different cluster nucleus than the one used by previous commands. The user's open transaction has been backed out. It is also possible that the user had already been timed out earlier. Action: Restart the transaction and any open read sequences. The user's command was routed to a different cluster nucleus than the one used by previous commands. The user had owned EXU or EXF control over one or more files or had started the Adabas session with an OP command with R-option. As a consequence of creating a new session for the user with the new nucleus, the EXU/EXF control or file list specified in the OP command are no longer in effect. Action: Restart the Adabas session with a new OP command. The user's command was routed to a different cluster nucleus than the one used by previous commands. The user had started the Adabas session with an OP command with ETID. As a consequence of creating a new session for the user with the new nucleus, the user is no longer associated with that ETID. Action: Restart the Adabas session with a new OP command. Adabas Transaction Manager Messages and Codes
Subcode Meaning 26 62 63 64 66 67 68 73 74 The user's command was routed to a different cluster nucleus than the one used by previous commands. Some cluster nucleus terminated abnormally while the new nucleus was creating a new session for the user. Action: Restart the Adabas session with a new OP command. An OP (open) command was issued without a user/ET ID, which is required for this type of application or environment. Action: Correct the program to specify a user/ET ID, and rerun the program. An OP command was given for an ET user not in ET status. The user is backed out with an Adabas-generated BT command, and the operation is closed. Action: Repeat the OP call. An OP command was issued with an 8-byte ET ID that already exists. An Adabas session with OPENRQ=YES was active and the user issued an Adabas command without having issued an OP command. Action: Ensure that all users issue an OP command as the first Adabas command. Insufficient Work part 1 space for open command with ETID definition when trying to read the user profile. The user queue element has been deleted. Most likely the command was thrown back due to ISN contention or space shortage. The space shortage is normally workpool space; if this is the case, the LWP parameter setting should be increased. This subcode is issued by Adabas Transaction Manager. The client session had an externally-controlled transaction, the outcome of which was “in doubt”. ATM forcibly resolved the “in doubt” transaction. There is a possibility that ATM’s resolution of the transaction might be inconsistent with the intended outcome. Check that the outcome of the session’s Adabas changes, in its previous transaction, was consistent with its changes to non-Adabas resources. Check the external transaction coordinator for reasons why the original transaction might have been left in the “in doubt” state. If the external coordinator indicates that the transaction was completed, and if the relevant system logs give no indication of the cause of the problem, contact your Software AG support representative. This subcode is issued by Adabas Transaction Manager. The client’s database session has lost its ETID. If a transaction was in progress, ATM attempted to back it out from all affected databases and release all held records. Issue a new OP command to the database. Adabas Transaction Manager Messages and Codes Adabas Response Codes 53
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 58 and 59: Adabas Response Codes 54 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 106 and 107:
Adabas Response Codes Response 87 O
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 ...

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

Delete template?

Save as template?