AionDS Messages and Codes Guide

More documents

Recommendations

Info

AionDS runtime errors 1-120 AionDS Messages and Codes This error is reported if: ■ the dataset is an RRDS ■ the dataset is a KSDS or an ESDS path residing in a separate File Owning Region, and the key position is not specified in the FCT .........................................................................................................................................................................................................˝.......................................... 20368 File is not open and/or unenabled AionDS is unable to open the dataset. Use the CEMT INQUIRE DATASET command to attempt to open the file. .........................................................................................................................................................................................................˝.......................................... 20369 Remote VSAM UNLOCK request failed An attempt to unlock a VSAM file defined to a CICS system has failed. .........................................................................................................................................................................................................˝.......................................... 20370 Remote MRO file requires specific VSAM type An attempt was made to access a file defined to a CICS region other than where the AAES transaction driver resides, but the AionDS file parameter did not specify the VSAM organization of the file (KSDS, RRDS, or ESDS). .........................................................................................................................................................................................................˝.......................................... 20373 DL/I request failed - DL/I language conflict CICS/VS rejected a DL/I request because of a conflict between the language being used and what was specified in the PSB. .........................................................................................................................................................................................................˝.......................................... 20374 DL/I request failed - PSB initialization failed The transaction driver attempted to schedule the PSB but the request failed when CICS/VS could not initialize the PSB. See the CICS/VS console log to determine the specific error CICS/VS encountered.
AionDS runtime errors .........................................................................................................................................................................................................˝.......................................... 20375 DL/I request failed - PSB not authorized CICS/VS rejected a DL/I request because the program was not authorized to issue that specific request. For example, if the transaction driver issued an ISRT request yet the PSB only authorized the program to retrieve segments, this error would be reported. .........................................................................................................................................................................................................˝.......................................... 20376 DL/I request failed - DL/I unscheduled termination A DL/I request was rejected due to an unscheduled termination. .........................................................................................................................................................................................................˝.......................................... 20377 DL/I request failed - DL/I function unscheduled A DL/I request was rejected and the function unscheduled. .........................................................................................................................................................................................................˝.......................................... 20378 DL/I request failed - DL/I UIBFCTR unknown CICS/VS returned a DL/I status condition that the transaction driver could not interpret. This condition normally represents a program error. The code was returned in UIBFCTR. .........................................................................................................................................................................................................˝.......................................... 20379 DL/I request failed - DL/I UIBDLTR unknown CICS/VS returned a DL/I status condition that the transaction driver could not interpret. This condition normally represents a program error. The code was returned in UIBDLTR. .........................................................................................................................................................................................................˝.......................................... 20380 Invalid segment name (0 or greater than 8 characters) A segment name must be a valid DL/I segment name. It must be between 1 and 8 characters, inclusive. AionDS Runtime Errors 1-121
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: AionDS runtime errors .............
Page 91 and 92: AionDS runtime errors Execution Con
Page 99 and 100: AionDS runtime errors At edit time
Page 113 and 114: AionDS runtime errors Reminder: In
Page 133: AionDS runtime errors .............
Page 145 and 146: AionDS runtime errors AionDS suppor
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:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
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 223 and 224:
Page 225 and 226:
CICS transaction driver messages No
Page 227 and 228:
Version 6.0-style messages (MSG600=
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
IMS and TSO transaction driver mess
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Chapter 3 CICS/VS Exception Conditi
Page 249 and 250:
CICS/VS exception conditions ......
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
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:
Page 287 and 288:
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

Create successful ePaper yourself

Delete template?

Save as template?