AionDS Messages and Codes Guide

More documents

Recommendations

Info

CICS/VS exception conditions .........................................................................................................................................................................................................˝.......................................... 1209 3-10 AionDS Messages and Codes Set error. MAES manages messages as a series of elements in a set. The transaction driver detected an invalid set sequence. For example, a middle-in-set was received following a last-in-set. This message reflects a program problem either in MAES/SAES or in a user-written external routine. Activate the MAESLOG and recreate the condition. The output of the MAESLOG will be used by PLATINUM Technical Support for AionDS to isolate the problem. .........................................................................................................................................................................................................˝.......................................... 1210 Record ID missing from a data request. The VSAM file request type requires a key, relative byte address, or relative record number. None of these were supplied. This is typically an application program error. .........................................................................................................................................................................................................˝.......................................... 1211 See the IBM CICS Application Programmer’s Reference Manual for information on INVALID TERMINAL IDENTIFIER and route list format. .........................................................................................................................................................................................................˝.......................................... 1212 See the IBM CICS Application Programmer’s Reference Manual for information on TERMINAL NOT SUPPORTED UNDER BMS and route list format. .........................................................................................................................................................................................................˝.......................................... 1213 See the IBM CICS Application Programmer’s Reference Manual for information on OPERATOR NOT SIGNED ON and route list format. .........................................................................................................................................................................................................˝.......................................... 1214 See the IBM CICS Application Programmer’s Reference Manual for information on OPERATOR SIGNED ON UNSUPPORTED TERMINAL and route list format. .........................................................................................................................................................................................................˝.......................................... 1215 See the IBM CICS Application Programmer’s Reference Manual for information on INVALID LCD MNEMONICS and route list format.
CICS/VS exception conditions .........................................................................................................................................................................................................˝.......................................... 1300 DL/I database not open. CICS/VS rejected a DL/I request because the database was not open. The CICS/VS console log should indicate why the database was not opened when CICS/VS was initialized. .........................................................................................................................................................................................................˝.......................................... 1301 Invalid DL/I call. A DL/I call was required but CICS/VS discovered an error before passing control to DL/I. The UIBFCTR field has been set to X'08' by CICS/VS. For more information: See the IBM CICS Application Programmer’s Reference Manual for information on DL/I interface response codes. .........................................................................................................................................................................................................˝.......................................... 1302 PCB address is invalid. A DL/I request was issued to CICS/VS but the address of the passed PCB was invalid. This condition represents an internal logic error in the transaction driver. .........................................................................................................................................................................................................˝.......................................... 1304 Scheduling conflict. The DL/I request was rejected due to a scheduling conflict. See the CICS/VS console log to determine the cause of the error. .........................................................................................................................................................................................................˝.......................................... 1305 Request for an invalid database. The DL/I request was rejected when CICS/VS could not find the database name in the FCT or the database was unopened as reflected in the FCT or an invalid argument was passed to DL/I. .........................................................................................................................................................................................................˝.......................................... 1306 PSB not found. The transaction driver attempted to allocate the PSB but instead was rejected when CICS/VS could not find the named PSB. CICS/VS Exception Conditions 3-11
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:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206: 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 247 and 248: Chapter 3 CICS/VS Exception Conditi
Page 249 and 250: CICS/VS exception conditions ......
Page 255: 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 299 and 300: MAESLOG messages Since this error r
Page 307 and 308:
MAESLOG messages ..................
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

Create successful ePaper yourself

Delete template?

Save as template?