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

More documents

Recommendations

Info

Adabas Response Codes Response 217 Origin Explanation Response 218 Origin Explanation Action Response 219 Origin Explanation 154 Mainframe systems only Command rejected by user exit. Note: If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (in the ACB) or the ACBXERRC field (in the ACBX) may contain the ID of the Entire Net-Work node that issued this response code. Mainframe systems only The following table describes the subcodes that appear with this response code, clarifying why the response was received. Subcode X'00' (00) X'48' (72) X'49' (73) X'4C' (76) X'4D' (77) Meaning The UB (TP monitor user block) pool is too small. There must be at least one user block for each concurrent user. This is controlled by the TP monitor link routines. The GETMAIN for the UB failed. An IPC message call parameter error occurred. This may indicate an internal product error or a TP-monitor storage overlay. Contact Software AG technical support for assistance. The IPC message caller did not provide a pointer to the extended user ID block. This is probably an internal product error. Contact Software AG technical support. The extended user ID data provided to the IPC Message Call is either binary zeroes or blank. This is probably and internal product error. Contact Software AG technical support. A getmain failed for the work area used in an IPC Message Call. Determine why the TP monitor is running short of storage. The storage will be acquired in the AMODE of the calling program, usually 31-bit for Natural transactions. Increase the UB pool by respecifying the NUBS parameter in the link routines. See the ADAGSET macro information in the Adabas Installation documentation. Mainframe systems only This response code should only occur when Adabas Transaction Manager is being used. Adabas Transaction Manager Messages and Codes
Response 220 Origin Subcode Meaning 2 3 4 5 6 7 8 9 10 11 12 20 The global transaction is not in the status that allows the call. Two transaction ID (XID) entries exist. The "R" and "J" options are not supported; or this is not a global transaction. The transaction ID (XID) does not exist or cannot be found (or example, when the given XID does not belong to the UQE). The record or value buffer definition may be invalid; for example, the length size may be invalid (less than or equal to 144 bytes); or the value buffer content may be invalid; for example, it may not contain a valid transaction ID (XID). The user is not an update or ET user or is already involved in a global transaction or the user is already on PET (preliminary end-of-transaction) status. A protocol error occurred: The user has been copied to Work 4 or the transaction was backed out. A protocol error occurred: The transaction was terminated or the user has no transaction ID (XID) or the recover call for an active user is not permitted. The system is currently locked due to a pending Work area 4 or DDWORKR4 overflow. The call is not permitted; either ADAEND or an ET-sync point is in process for the nucleus. Force the ATM nucleus to backout (BT) the transaction. The user has not made any updates. A preliminary ET command, therefore, is not permitted. A logic error occurred. The transaction ID (XID) is unknown. This error occurs only in a cluster environment. Mainframe systems only Explanation The request was rejected by Entire Net-Work due to a shortage of short term buffers. Action Note: If you are running with Entire Net-Work, the leftmost two bytes of the Additions 2 field (in the ACB) or the ACBXERRC field (in the ACBX) may contain the ID of the Entire Net-Work node that issued this response code. For BS2000 systems running Sockets 2.2 or later, check the address space limit using the SHOW-USER-ATTRIBUTES command in the field ADDRESS-SPACE-LIMIT (the value is in megabytes). If necessary, increase it using the MODIFY-USER-ATTRIBUTES command from a privileged user ID. For BS2000 systems running Sockets 2.1 or earlier, increase the CMSIZE parameter to enlarge the common memory pool, as long as there is enough room in the address space. Then restart Entire Net-Work. For z/OS and z/VSE, increase the region size. Adabas Transaction Manager Messages and Codes Adabas Response Codes 155
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 56 and 57:
Adabas Response Codes 52 Subcode Me
Page 58 and 59:
Page 60 and 61:
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: Adabas Response Codes Response 94 O
Page 110 and 111: Adabas Response Codes 106 Subcode M
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 132 and 133: Adabas Response Codes Action 128 Su
Page 138 and 139: Adabas Response Codes 134 Subcode O
Page 140 and 141: Adabas Response Codes 136 Subcode O
Page 192 and 193: 188
Page 194 and 195: User Abend Codes Code Module 27 28
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?