AionDS Messages and Codes Guide

More documents

Recommendations

Info

IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... 40 2-20 AionDS Messages and Codes OPNDST failed on node xxxxxxxx with RTNCD = rr and FDBK = ff The OPNDST VTAM function failed during the initialization of the session with MAES. The message includes the return code from the RPL (rr) and the code in the RPLFDBK2 field (ff). .........................................................................................................................................................................................................˝.......................................... 44 ACB not OPEN when terminating the session The ACB was not open when IAESTERM was called. Either the ACB was not opened by the AionDS transaction driver, or the session terminated and AionDS did not detect and handle the termination properly. .........................................................................................................................................................................................................˝.......................................... 48 CLSDST failed IAESTERM issues this message and other diagnostic information when a CLSDST fails. .........................................................................................................................................................................................................˝.......................................... 52 SEND failed IAESTERM and IAESSEND issue this message and other diagnostic information when a SEND fails. .........................................................................................................................................................................................................˝.......................................... 56 RECEIVE failed IAESTERM and IAESGET issue this message and other diagnostic information when a RECEIVE fails. .........................................................................................................................................................................................................˝.......................................... 60 Subroutine failed to complete its processing This informational message is preceded by other messages which identify the reason why the subroutine failed to complete.
IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... 64 Consultation stopped due to internal error Failure of an internal component has caused the transaction driver to terminate. Look for error messages in the JES job log and report the problem to PLATINUM Technical Support for AionDS. .........................................................................................................................................................................................................˝.......................................... 68 Unknown message type received - mm rr An unrecognized message was received. The AionDS/IMS transaction driver expects a header at the beginning of each message. The header contains values which identify the data that follows. The message includes the value found the AESMTYPE field (mm), and the value found in the AESMREQ field (rr). The value in the AESMTYPE field was not recognized by the transaction driver. .........................................................................................................................................................................................................˝.......................................... 72 VTAM error encountered - RTNCD = rrr and FDBK = fff The message includes the return code (rrr) and the feedback information (fff) from the VTAM RPL. .........................................................................................................................................................................................................˝.......................................... 76 LU name for VTAM missing from PDBs This internal error message is issued by ADSFPL when an application program attempts to invoke a MAES-resident knowledge base without passing in a parameter descriptor block containing the VTAM node name. .........................................................................................................................................................................................................˝.......................................... 84 Node xxxxxxxx is inactive. Consultation cannot continue A consultation attempted to resume, but the MAES node that was processing that consultation is no longer active. .........................................................................................................................................................................................................˝.......................................... 88 No node name available for the transaction driver The VTAM node names to be used by ADSFPL were unavailable or not defined. The request by the user application program failed. Transaction Driver Messages 2-21
Page 1:
Messages and Codes PLATINUM technol
Page 5 and 6:
Preface How to Use This Manual Tabl
Page 7 and 8:
How to Use This Manual ............
Page 9 and 10:
...................................
Page 11 and 12:
...................................
Page 13 and 14:
■ You must use other characters,
Page 15 and 16:
Chapter 1 AionDS Runtime Errors ...
Page 17 and 18:
Overview ..........................
Page 19 and 20:
Table of error messages %Currentcla
Page 21 and 22:
Table of error messages Argument to
Page 23 and 24:
Table of error messages Can’t loa
Page 25 and 26:
Table of error messages Dataset not
Page 27 and 28:
Table of error messages Element wit
Page 29 and 30:
Table of error messages Forwardchai
Page 31 and 32:
Table of error messages Incorrect k
Page 33 and 34:
Table of error messages Invalid cur
Page 35 and 36:
Table of error messages Invalid or
Page 37 and 38:
Table of error messages It is not p
Page 39 and 40:
Table of error messages No current
Page 41 and 42:
Table of error messages Problem rea
Page 43 and 44:
Table of error messages SAESGET VTA
Page 45 and 46:
Table of error messages Static inst
Page 47 and 48:
Table of error messages Unable to c
Page 49 and 50:
Table of error messages Unexpected
Page 51 and 52:
Table for converting error codes Ta
Page 53 and 54:
Table for converting error codes 14
Page 55 and 56:
32553 20353 Remote VSAM PUT request
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
AionDS runtime errors AionDS runtim
Page 63 and 64:
AionDS runtime errors If the user c
Page 65 and 66:
AionDS runtime errors other a posit
Page 67 and 68:
AionDS runtime errors Note: If the
Page 69 and 70:
AionDS runtime errors .............
Page 71 and 72:
The graph is not displayed. AionDS
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
AionDS runtime errors To correct th
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
AionDS runtime errors Execution Con
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
AionDS runtime errors At edit time
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
AionDS runtime errors Reminder: In
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
AionDS runtime errors AionDS suppor
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186: AionDS runtime errors .............
Page 217 and 218: Chapter 2 Transaction Driver Messag
Page 219 and 220: Post Version 6.00-style messages (M
Page 221 and 222: CICS transaction driver messages ..
Page 225 and 226: CICS transaction driver messages No
Page 227 and 228: Version 6.0-style messages (MSG600=
Page 233 and 234: IMS and TSO transaction driver mess
Page 235: IMS and TSO transaction driver mess
Page 247 and 248: Chapter 3 CICS/VS Exception Conditi
Page 249 and 250: CICS/VS exception conditions ......
Page 261 and 262: Chapter 4 DB/DC Program Interface R
Page 263 and 264: ADSMSW (Message switching function)
Page 265 and 266: ADSULINK (User link facility) .....
Page 267 and 268: ADSPSB (Schedule a new PSB - AionDS
Page 269 and 270: Chapter 5 MAES Error Codes ........
Page 271 and 272: Code number Description 202 3270 Da
Page 273 and 274: continued Return Code Description 3
Page 275 and 276: continued Return code Description 1
Page 277 and 278: Status Codes MAES-specific codes ..
Page 279 and 280: Chapter 6 MAESLOG Messages ........
Page 281 and 282: MAESLOG messages The following list
Page 283 and 284: MAESLOG messages ..................
Page 285 and 286: MAESLOG messages ..................
Page 287 and 288:
MAESLOG messages ..................
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
MAESLOG messages Since this error r
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
MAESLOG messages ■ The node is ac
Page 323 and 324:
Page 325 and 326:
Page 327 and 328:
Page 329 and 330:
Page 331 and 332:
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Chapter 7 AionDS Fatal System Error
Page 339 and 340:
Overview Only at edit time can the
Page 341 and 342:
Fatal system errors ...............
Page 343 and 344:
Page 345 and 346:
Page 347 and 348:
Chapter 8 AionDS System Log .......
Page 349 and 350:
Examining the system log database T
Page 351 and 352:
Execution messages Examining the sy
Page 353 and 354:
Consultation messages Examining the
Page 355 and 356:
Examining the system log ..........
Page 357 and 358:
Examining the system log ..........
Page 359 and 360:
DL/I Messages Examining the system
Page 361:
AionDS Messages and Codes DC0431
show all

AionDS Messages and Codes Guide

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

Delete template?

Save as template?