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

More documents

Recommendations

Info

Adabas Response Codes Action Response 42 Origin Explanation 74 ■ Invalid index usage; ■ A descending index range was specified; ■ A double index was used for a non-periodic field; ■ A multiple-value field with an index specification and a multiple-value field without an index specification were used; ■ A value cannot be converted to the required format (READ command) or converted to the FDT standard format (UPDATE command); ■ The S element was applied to a field that does not have the NC option; ■ A field with the NC option was used more than once together with its S element; ■ The add option is not compatible with the format/length; ■ The specification of a charater set was invalid; ■ A field was specified with an edit mask not allowed for the field; ■ A field segment notation (byte-number,length) or (byte-number,length,length-2) was not correct. Values for byte-number + length must be less than or equal to the maximum value length + 1, and length-2 must be equal to length. The maximum value for LB fields is 2,147,483,643, for LA fields 16381, an for other values 253 bytes; ■ Segment notation is only allowed for values with the format "A". The following information is returned in the Additions 2 field of the control block: ■ The leftmost two bytes contain the number of the byte (in binary format) relative to the beginning of the format buffer where the error was detected. ■ The rightmost two bytes contain the name of the field being processed when the error was detected. Correct the specification error and reissue the command or job. For more information about syntax rules for multiple field and periodic group indexing, refer to the Adabas Command Reference documentation. Mainframe systems only A space problem occurred. The following are the subcodes and their meanings: Subcode Meaning 1 2 The Work pool was too small to store a user format. Action: Increase the LWP specification and retry . The internal format buffer was too small to store a user format (translated into internal structure). Action: Increase LFP specification and retry. Adabas Transaction Manager Messages and Codes
Action Response 43 Origin Explanation Action Response 44 Origin See the actions described in the subcodes. Mainframe and open systems In an L9 command, the descriptor specified in the format buffer did not agree with the descriptor specified in the search buffer. Correct the format buffer or the search buffer. Mainframe and open systems Explanation The meaning of this response code varies, depending on whether you are using Adabas on mainframe systems or Adabas on open systems. Mainframe Systems One of the following format buffer errors occurred (subcodes are shown in the leftmost column): Subcode Meaning 1 2 3 4 5 6 7 8 9 10 12 Open Systems The specified format is not allowed for an update operation. A possible reason for this is the presence of a conditional format buffer with an update operation. The L9 command's format buffer format is not allowed for other commands. The specified format is not allowed for an update operation. A possible reason for this is the presence of a conditional format buffer with an update operation. The L9 command's format buffer format is not allowed for other commands. Format used for L9 can only contain field and an optional daylight savings time indicator (fldD). Fixed point format must have length 2, 4, or 8. Conditional format and more than one format buffer was specified. The current Adabas call provides a different number of format buffers than the format reference by CID. Number of format buffer segments (ABDs) is zero. AAS,AA,AA is invalid. L option specified but the format has no LOB segment with *-position. One of the following situations occurred: Adabas Transaction Manager Messages and Codes Adabas Response Codes 75
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 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 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 120 and 121: Adabas Response Codes Response 130
Page 128 and 129:
Adabas Response Codes 124 Subcode M
Page 130 and 131:
Adabas Response Codes Action Respon
Page 132 and 133:
Adabas Response Codes Action 128 Su
Page 134 and 135:
Adabas Response Codes Response 144
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:
Adabas Response Codes 162 Subcode 8
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?