AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
AionDS runtime errors .........................................................................................................................................................................................................˝.......................................... 1359 1-64 AionDS Messages and Codes Object referenced in CM function is non-simple and can’t be sourced AionDS cannot execute a CM statement for the specified object because the object is too complex to be displayed on a single screen. The most complex object AionDS can display is a list of records in which all fields have basic data types. .........................................................................................................................................................................................................˝.......................................... 1360 Class must have an attached display to be sourced AionDS is unable to source values for the class because the class has no attached display. .........................................................................................................................................................................................................˝.......................................... 1361 Class contains list or set slots; may not be sourced AionDS cannot execute a CM or ASK statement for the specified class because the class is too complex to be displayed on a single screen. The most complex class that AionDS can display is one in which all slots have basic data types. .........................................................................................................................................................................................................˝.......................................... 1362 Illegal comparison - types are not compatible AionDS is unable to compare the values of an instance with those of an instance of another class. The comparison fails because there is a slot in one class that has the same position as a slot in the other class, but the type definition for these slots is different. For example, this error occurs if the third slot of one class has a different type than the third slot of the other class. .........................................................................................................................................................................................................˝.......................................... 1363 Class may not be loaded at this time; FLUSH required AionDS is unable to execute the DBMS(LOAD) statement because instances are already loaded in memory. The instances in memory may have been loaded as a result of a DBMS(LOAD) statement, or they may have been loaded automatically. This error can also occur if AionDS has created instances, and executed a DBMS(UPDATE) statement.
AionDS runtime errors To correct this situation, execute the DBMS(FLUSH) statement before loading instances. .........................................................................................................................................................................................................˝.......................................... 1364 Invalid window handle passed to CM Function AionDS is unable to execute the CM statement because there is no window on the current screen with the specified handle. Check that the integer for the window handle is not hard-coded and that the variable that holds the handle is updated correctly. You can use CM GETCURSOR, CM GETWINDOW, or CM GETWINDOWLIST to get valid window handles. .........................................................................................................................................................................................................˝.......................................... 1365 Bad argument passed to the SET function The referenced slot is UNKNOWN. Check if the correct pointer and slot reference were specified. .........................................................................................................................................................................................................˝.......................................... 1366 Bad argument passed to the INDEX function The KDL INDEX statement specifies a non-existent index, such as zero. .........................................................................................................................................................................................................˝.......................................... 1367 DBMS function aborted; Class already in process AionDS is unable to execute a DBMS statement because it is already in the process of loading or updating the database. This can be due to a WHENLOADED demon that tries to execute a DBMS statement. .........................................................................................................................................................................................................˝.......................................... 1368 Bad argument passed to the READSTR or WRITESTR function One of the arguments to a READSTR or WRITESTR function was UNKNOWN or constant. An attempt was made to coerce an UNKNOWN or constant value into or out of the buffer. The statement is skipped. AionDS Runtime Errors 1-65
- 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 and 60: Table for converting error codes 37
- 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: AionDS runtime errors .............
- Page 75 and 76: AionDS runtime errors .............
- Page 77: AionDS runtime errors .............
- 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 .............
- Page 111 and 112: AionDS runtime errors .............
- Page 113 and 114: AionDS runtime errors Reminder: In
- Page 115 and 116: AionDS runtime errors .............
- Page 117 and 118: AionDS runtime errors .............
- Page 119 and 120: AionDS runtime errors .............
- Page 121 and 122: AionDS runtime errors .............
- Page 123 and 124: AionDS runtime errors .............
- Page 125 and 126: AionDS runtime errors .............
- Page 127 and 128: AionDS runtime errors .............
<strong>AionDS</strong> runtime errors<br />
To correct this situation, execute the DBMS(FLUSH) statement before<br />
loading instances.<br />
.........................................................................................................................................................................................................˝..........................................<br />
1364<br />
Invalid window h<strong>and</strong>le passed to CM Function<br />
<strong>AionDS</strong> is unable to execute the CM statement because there is no window<br />
on the current screen with the specified h<strong>and</strong>le. Check that the integer for<br />
the window h<strong>and</strong>le is not hard-coded <strong>and</strong> that the variable that holds the<br />
h<strong>and</strong>le is updated correctly. You can use CM GETCURSOR, CM<br />
GETWINDOW, or CM GETWINDOWLIST to get valid window h<strong>and</strong>les.<br />
.........................................................................................................................................................................................................˝..........................................<br />
1365<br />
Bad argument passed to the SET function<br />
The referenced slot is UNKNOWN. Check if the correct pointer <strong>and</strong> slot<br />
reference were specified.<br />
.........................................................................................................................................................................................................˝..........................................<br />
1366<br />
Bad argument passed to the INDEX function<br />
The KDL INDEX statement specifies a non-existent index, such as zero.<br />
.........................................................................................................................................................................................................˝..........................................<br />
1367<br />
DBMS function aborted; Class already in process<br />
<strong>AionDS</strong> is unable to execute a DBMS statement because it is already in the<br />
process of loading or updating the database. This can be due to a<br />
WHENLOADED demon that tries to execute a DBMS statement.<br />
.........................................................................................................................................................................................................˝..........................................<br />
1368<br />
Bad argument passed to the READSTR or WRITESTR function<br />
One of the arguments to a READSTR or WRITESTR function was<br />
UNKNOWN or constant. An attempt was made to coerce an UNKNOWN<br />
or constant value into or out of the buffer.<br />
The statement is skipped.<br />
<strong>AionDS</strong> Runtime Errors 1-65