AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
AionDS runtime errors .........................................................................................................................................................................................................˝.......................................... 983 1-50 AionDS Messages and Codes SQL string is unknown The first argument to the KDL SQL statement contains a parameter that is UNKNOWN. Check the use of the parameter. .........................................................................................................................................................................................................˝.......................................... 1000 Illegal assignment At edit time, this error is reported when the user tries to use the “(*)” syntax to assign to all elements of a list; for example, (*) is 'red' At runtime, this error can occur under the following circumstances: ■ when an invalid assignment is made to a list element, such as assigning a value to list element that is not defined within a function; for example, list_pa(j) is 5 /*illegal when j is unknown*/ ■ when an assignment is made to a file parameter and the file is not open; for example, file_pa->.field is 10 /*fails if file_pa is not open*/ Note: If the knowledge base has been optimized using HPO, this error is not reported and the assignment is ignored. .........................................................................................................................................................................................................˝.......................................... 1001 Error passing parameters into the state When passing parameters into a state, AionDS performs an assignment of the arguments to the state’s input parameters. This error is reported if the assignment cannot be performed because the input parameter already has a value (in the Facts property), or because of a type inconsistency. The assignment is ignored. If the input parameter already has a value, the value is unchanged. If the input parameter does not have a value, its value remains UNKNOWN. All other parameter passing is completed normally. Be sure the input parameter and the argument are of the same type (and not just compatible ones). For instance, making one of them an integer and the
AionDS runtime errors other a positive integer (“>0”) is acceptable for the type checker, but it will produce problems if the argument evaluates to a negative integer. Avoid giving a value in the Facts property of the input parameter unless the parameter is a Value Can Change parameter. Note: If the knowledge base has been optimized using HPO, this error is not reported and the assignment is allowed. .........................................................................................................................................................................................................˝.......................................... 1002 Error returning parameters from the state When returning parameters from a state, AionDS performs an assignment of the state’s output parameters to the proper argument parameters. This error is reported if the assignment cannot be performed because the proper argument already has a value, or because of a type inconsistency. The assignment is ignored. If the argument parameter already has a value, the value is unchanged. If the argument parameter does not have a value, its value remains UNKNOWN. All other parameter passing is completed normally. Be sure the output parameter and the argument are of the same type (and not just compatible ones). For instance, making one of them an integer and the other a positive integer (“>0”) is acceptable for the type checker, but it will produce problems if the output parameter evaluates to a negative integer. The argument parameter should not have a value before the STATE step unless it is a Value Can Change parameter. Note: If the knowledge base has been optimized using HPO, this error is not reported and the assignment is allowed. .........................................................................................................................................................................................................˝.......................................... 1003 New constraint inconsistent with existing constraint A constraint operation is not consistent with the previous constraints on the parameter (for example, constraining a positive integer to be a negative value). The constraint operation is ignored. AionDS Runtime Errors 1-51
- 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 and 60: Table for converting error codes 37
- Page 61 and 62: AionDS runtime errors AionDS runtim
- Page 63: AionDS runtime errors If the user c
- 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 .............
- Page 111 and 112: AionDS runtime errors .............
- Page 113 and 114: AionDS runtime errors Reminder: In
<strong>AionDS</strong> runtime errors<br />
.........................................................................................................................................................................................................˝..........................................<br />
983<br />
1-50 <strong>AionDS</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
SQL string is unknown<br />
The first argument to the KDL SQL statement contains a parameter that is<br />
UNKNOWN. Check the use of the parameter.<br />
.........................................................................................................................................................................................................˝..........................................<br />
1000<br />
Illegal assignment<br />
At edit time, this error is reported when the user tries to use the “(*)” syntax<br />
to assign to all elements of a list; for example,<br />
(*) is 'red'<br />
At runtime, this error can occur under the following circumstances:<br />
■ when an invalid assignment is made to a list element, such as assigning a<br />
value to list element that is not defined within a function; for example,<br />
list_pa(j) is 5 /*illegal when j is unknown*/<br />
■ when an assignment is made to a file parameter <strong>and</strong> the file is not open;<br />
for example,<br />
file_pa->.field is 10 /*fails if file_pa is not open*/<br />
Note: If the knowledge base has been optimized using HPO, this error is not<br />
reported <strong>and</strong> the assignment is ignored.<br />
.........................................................................................................................................................................................................˝..........................................<br />
1001<br />
Error passing parameters into the state<br />
When passing parameters into a state, <strong>AionDS</strong> performs an assignment of the<br />
arguments to the state’s input parameters. This error is reported if the<br />
assignment cannot be performed because the input parameter already has a<br />
value (in the Facts property), or because of a type inconsistency.<br />
The assignment is ignored. If the input parameter already has a value, the<br />
value is unchanged. If the input parameter does not have a value, its value<br />
remains UNKNOWN. All other parameter passing is completed normally.<br />
Be sure the input parameter <strong>and</strong> the argument are of the same type (<strong>and</strong> not<br />
just compatible ones). For instance, making one of them an integer <strong>and</strong> the