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

More documents

Recommendations

Info

Adabas Response Codes 60 Subcode 6 7 8 9 10 11 12 13 14 15 16 17 18 21 22 Meaning On mainframe systems, an E1 (delete record) command was given without specifying a valid file number. On open systems, the file to be created already exists. The program tried to perform an LF command on system file 1 or 2. On mainframe systems, the program tried to access a file that was not listed in the file list of an open (OP) executed with the R option. On open systems, \an ET user with a restricted file list and ACC = file number attempted to issue a UPD command, or a user with a restricted file list attempted to touch a file that is not in the file list The file that the program attempted to access is completely locked. This is usually because the maximum number of logical file extents that can fit into the FCB have been used. Action: Reorder, then unlock the file. Continue operation. The program attempted to access a file which is locked with exclusive EXU status. An LF command (read FDT) was run on a file that is not loaded; neither the FCB nor the FDT exists. File has been locked with LOCKF. A file is password-protected and the password was specified, but the corresponding security file is missing (not loaded). A command was issued against a LOB file. Commands involving LB fields should be directed against the associated base file, not the LOB file. A file is being loaded so its information is temporarily unavailable. On mainframe systems, an attempt was made to perform an update (e.g. A1, E1, N1/2) against a file loaded with the attribute RPLUPDATEONLY=YES. On open systems, the file was locked by ADAOPR. An attempt was made to perform an update (e.g. A1, E1, N1/2) against a file loaded with the attribute READONLY=YES. File has been locked with ALOCKF. On mainframe systems, there was not enough space for encoding elements (ECSE). On open systems, a two-byte file number was used against a lower version database that does not support large file numbers. On mainframe systems, the required ECS objects needed for conversion between user and system data representation could not be loaded. On open systems, the file control block (FCB) is invalid (corrupted). Adabas Transaction Manager Messages and Codes
Response 18 Origin Explanation Action Subcode 23 24 25 29 52 99 249 (0x00F9) Meaning ECS object could not be located. The following objects must be available in the encoding objects library: File Alpha, File Wide EDD, User Alpha, User Wide EDD, and the PTOs for the combinations between file/user alpha/wide encodings. Action: Check that the required EDD and PTO objects are available. ECS function get_attribute() failed. Action: The function's return code is logged with the nucleus message ADAN7A. One of the following occurred: - A required encoding attribute was missing in an ECS object (encoding type, class, and flags) - The default space character length was > 4 - Default space table allocation failed - If DBCS-only plane exists, wide space character was undefined, or the length > 4, or wide space table allocation failed An Adabas Review communication error has occurred. Contact your Software AG support representative. A non-Adabas target was called. The file's FTD is corrupted. Action: To resolve the problem, repair the file by running a restore/regenerate from a consistent state. While attempting to satisfy a partitioned file command, Adabas Vista detected the unavailability of an FDT – this is invalid for one of the following reasons: ■ None of the partitions were available/online and at least one of them has the file parameter Critical set to YES. ■ None of the partitions were available/online and all of them have the file parameter Critical set to NO and the command can not be satisfied with a “no data” response such as RSP003. An error occurred when Adabas Vista (open systems) tried to access a file that was not listed in the file list of an OP command executed with the R option. Action: Ensure at least one of the file partitions is available/online or review the program logic. Mainframe and open systems. Invalid file number usage. The file number was modified between successive L2/L5 calls or between successive Lx and Sx calls. Correct the file number. Adabas Transaction Manager Messages and Codes Adabas Response Codes 61
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 62 and 63: Adabas Response Codes Action 58 ■
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 110 and 111: Adabas Response Codes 106 Subcode M
Page 112 and 113: Adabas Response Codes 108 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 120 and 121:
Page 122 and 123:
Adabas Response Codes 118 Subcode M
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?