AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
Table for converting error codes 1-46 AionDS Messages and Codes 37347 20419 Invalid remote SQL interface; valid values are "IBM" and "DB2" (WIN/OS2/PM) 37348 20417 Unable to load support library for VAX Rdb/VMS 37349 20418 Unable to load support library for Microsoft/Sybase SQL Server 37350 20415 Unable to load support library for IBM Database Manager 37351 20416 Unable to load support library for Oracle 46441 20311 I/O operation not supported by access method 46442 20310 I/O operation not supported for this dataset type 46443 20313 Incorrect key location 46444 20314 Incorrect key length 46445 20315 Invalid generic key length 46450 20350 Remote VSAM OPEN request failed 46451 20351 Remote VSAM CLOSE request failed 46452 20352 Remote VSAM GET request failed 46453 20353 Remote VSAM PUT request failed 46454 20354 Remote VSAM ERASE request failed 46455 20355 Remote VSAM SELECT request failed 46456 20359 Remote VSAM GET returned DUPKEY condition 46465 20365 The SELECT format used is valid only for READ mode 46466 20366 The requested I/O operation requires a key 46468 20368 File is not open and/or unenabled 46469 20369 Remote VSAM UNLOCK request failed 46470 20370 Remote MRO file requires specific VSAM type
AionDS runtime errors AionDS runtime errors .........................................................................................................................................................................................................˝.......................................... Overview This section explains the runtime error messages that are issued by AionDS, HPO, ADSAPI, AAPI/CICS and AAPI/IMS. Error messages issued by the AionDS/CICS and AionDS/IMS transaction drivers, as well as MAES, are not included in this chapter. For more information: See “How to Use This Manual” for information about where to find these messages. The errors are listed by error code in ascending order. For more information about determining the correct error code, see the previous section. In IMS, some error codes may include a 2-digit prefix. This prefix is a VTAM error code described in the section “IMS and TSO transaction driver messages” in Chapter 2. Caution: Some message codes use the same number as another message’s error code. This can cause confusion if you look for the message under the message code instead of the error code. If the message description seems inappropriate for your situation, check the numbers in the section “Table for converting error codes” on page 1-37. .........................................................................................................................................................................................................˝.......................................... 540 Invalid placement of Thousands-Separator This is a data validation error. The user entered a numeric value incorrectly. For example: 12,00 should be 1,200. .........................................................................................................................................................................................................˝.......................................... 692 Invalid stored answer file format The format of the file is incorrect. AionDS does not run the consultation. Check the specified file to make sure that it’s an AionDS stored answer file. AionDS Runtime Errors 1-47
- 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: Table for converting error codes 34
- Page 59: Table for converting error codes 37
- 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: AionDS runtime errors .............
- Page 75 and 76: AionDS runtime errors .............
- Page 77 and 78: AionDS runtime errors .............
- Page 79 and 80: AionDS runtime errors To correct th
- Page 81 and 82: AionDS runtime errors .............
- Page 83 and 84: AionDS runtime errors .............
- Page 85 and 86: AionDS runtime errors .............
- Page 87 and 88: AionDS runtime errors .............
- Page 89 and 90: AionDS runtime errors .............
- Page 91 and 92: AionDS runtime errors Execution Con
- Page 93 and 94: AionDS runtime errors .............
- Page 95 and 96: AionDS runtime errors .............
- Page 97 and 98: AionDS runtime errors .............
- Page 99 and 100: AionDS runtime errors At edit time
- Page 101 and 102: AionDS runtime errors .............
- Page 103 and 104: AionDS runtime errors .............
- Page 105 and 106: AionDS runtime errors .............
- Page 107 and 108: AionDS runtime errors .............
- Page 109 and 110: AionDS runtime errors .............
Table for converting error codes<br />
1-46 <strong>AionDS</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
37347 20419 Invalid remote SQL interface; valid values are "IBM" <strong>and</strong><br />
"DB2" (WIN/OS2/PM)<br />
37348 20417 Unable to load support library for VAX Rdb/VMS<br />
37349 20418 Unable to load support library for Microsoft/Sybase SQL Server<br />
37350 20415 Unable to load support library for IBM Database Manager<br />
37351 20416 Unable to load support library for Oracle<br />
46441 20311 I/O operation not supported by access method<br />
46442 20310 I/O operation not supported for this dataset type<br />
46443 20313 Incorrect key location<br />
46444 20314 Incorrect key length<br />
46445 20315 Invalid generic key length<br />
46450 20350 Remote VSAM OPEN request failed<br />
46451 20351 Remote VSAM CLOSE request failed<br />
46452 20352 Remote VSAM GET request failed<br />
46453 20353 Remote VSAM PUT request failed<br />
46454 20354 Remote VSAM ERASE request failed<br />
46455 20355 Remote VSAM SELECT request failed<br />
46456 20359 Remote VSAM GET returned DUPKEY condition<br />
46465 20365 The SELECT format used is valid only for READ mode<br />
46466 20366 The requested I/O operation requires a key<br />
46468 20368 File is not open <strong>and</strong>/or unenabled<br />
46469 20369 Remote VSAM UNLOCK request failed<br />
46470 20370 Remote MRO file requires specific VSAM type