AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
AionDS runtime errors .........................................................................................................................................................................................................˝.......................................... 50702 1-194 AionDS Messages and Codes Invalid record I/O option string given An invalid option was passed to an I/O function. Check the function syntax. .........................................................................................................................................................................................................˝.......................................... 50703 Invalid record I/O get mode given An invalid get mode was specified in a GETREC statement. Check the syntax for GETREC. .........................................................................................................................................................................................................˝.......................................... 50706 Invalid I/O operation; GETREC returned EOF An attempt was made to execute an I/O function after the EOF function returned an end-of-file condition. .........................................................................................................................................................................................................˝.......................................... 50709 Invalid OPENFILE request; duplicate record name specified A duplicate record name was specified in an OPENFILE statement. AionDS already has a file parameter open for that record name. .........................................................................................................................................................................................................˝.......................................... 51001 EXITSTATE used outside of agenda; use /e command-line switch (PC/WIN/OS2/PM/SUN/AIX) A KDL property that is not a state’s agenda contains the EXITSTATE statement. You must pass the /E switch to HPO or HPOOPT. Because this switch results in slightly larger and slower code, you should avoid using it if possible. Instead make sure you use EXITSTATE in agendas only.
AionDS runtime errors .........................................................................................................................................................................................................˝.......................................... 51001 EXITSTATE used outside of agenda; use EXIT option with KBOPT (MVS/VM) A KDL property that is not a state’s agenda contains the EXITSTATE statement. You must assign the value of EXIT to the execution symbolic parameter P in the KBOPT or KBOPT1 JCL. Because this switch results in slightly larger and slower code, you should avoid using it if possible. Instead make sure that you use EXITSTATE in agendas only. .........................................................................................................................................................................................................˝.......................................... 51002 Unrecognized or unsupported KDL statement; import KB with High- Performance ON The knowledge base contains a statement that HPO does not support. All such statements are listed in Chapter 2 of the HPO Installation and Operation Guide for your environment. Before optimizing a knowledge base, you should always set the HIGH- PERFORMANCE profile option to ON and import the knowledge base. This will tell you if there are any statements in the knowledge base that HPO does not support. .........................................................................................................................................................................................................˝.......................................... 51003 Context too large; recompile using /o switch, with a higher argument A state or class contains more KDL than the Optimizer can compile. Try rerunning the HPO Optimizer using the /O switch. Give a higher argument to /O than the default. .........................................................................................................................................................................................................˝.......................................... 51004 Too many unique string constants in a context A state or class contains too many unique string constants. Try breaking up the state or class into two or more states or classes. AionDS Runtime Errors 1-195
- Page 157 and 158: AionDS runtime errors .............
- Page 159 and 160: AionDS runtime errors .............
- Page 161 and 162: AionDS runtime errors .............
- Page 163 and 164: AionDS runtime errors .............
- Page 165 and 166: AionDS runtime errors .............
- Page 167 and 168: AionDS runtime errors .............
- Page 169 and 170: AionDS runtime errors .............
- Page 171 and 172: AionDS runtime errors .............
- Page 173 and 174: AionDS runtime errors .............
- Page 175 and 176: AionDS runtime errors .............
- Page 177 and 178: AionDS runtime errors .............
- Page 179 and 180: AionDS runtime errors .............
- Page 181 and 182: AionDS runtime errors .............
- Page 183 and 184: AionDS runtime errors .............
- Page 185 and 186: AionDS runtime errors .............
- Page 187 and 188: AionDS runtime errors .............
- Page 189 and 190: AionDS runtime errors .............
- Page 191 and 192: AionDS runtime errors .............
- Page 193 and 194: AionDS runtime errors .............
- Page 195 and 196: AionDS runtime errors .............
- Page 197 and 198: AionDS runtime errors .............
- Page 199 and 200: AionDS runtime errors .............
- Page 201 and 202: AionDS runtime errors .............
- Page 203 and 204: AionDS runtime errors .............
- Page 205 and 206: AionDS runtime errors .............
- Page 207: AionDS runtime errors .............
- Page 211 and 212: AionDS runtime errors .............
- Page 213 and 214: AionDS runtime errors .............
- Page 215 and 216: 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 223 and 224: CICS transaction driver messages ..
- Page 225 and 226: CICS transaction driver messages No
- Page 227 and 228: Version 6.0-style messages (MSG600=
- Page 229 and 230: CICS transaction driver messages ..
- Page 231 and 232: CICS transaction driver messages ..
- Page 233 and 234: IMS and TSO transaction driver mess
- Page 235 and 236: IMS and TSO transaction driver mess
- Page 237 and 238: IMS and TSO transaction driver mess
- Page 239 and 240: IMS and TSO transaction driver mess
- Page 241 and 242: IMS and TSO transaction driver mess
- Page 243 and 244: IMS and TSO transaction driver mess
- Page 245 and 246: 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 251 and 252: CICS/VS exception conditions ......
- Page 253 and 254: CICS/VS exception conditions ......
- Page 255 and 256: CICS/VS exception conditions ......
- Page 257 and 258: CICS/VS exception conditions ......
<strong>AionDS</strong> runtime errors<br />
.........................................................................................................................................................................................................˝..........................................<br />
51001<br />
EXITSTATE used outside of agenda; use EXIT option with KBOPT<br />
(MVS/VM)<br />
A KDL property that is not a state’s agenda contains the EXITSTATE<br />
statement.<br />
You must assign the value of EXIT to the execution symbolic parameter P in<br />
the KBOPT or KBOPT1 JCL. Because this switch results in slightly larger<br />
<strong>and</strong> slower code, you should avoid using it if possible. Instead make sure that<br />
you use EXITSTATE in agendas only.<br />
.........................................................................................................................................................................................................˝..........................................<br />
51002<br />
Unrecognized or unsupported KDL statement; import KB with High-<br />
Performance ON<br />
The knowledge base contains a statement that HPO does not support. All<br />
such statements are listed in Chapter 2 of the HPO Installation <strong>and</strong> Operation<br />
<strong>Guide</strong> for your environment.<br />
Before optimizing a knowledge base, you should always set the HIGH-<br />
PERFORMANCE profile option to ON <strong>and</strong> import the knowledge base.<br />
This will tell you if there are any statements in the knowledge base that HPO<br />
does not support.<br />
.........................................................................................................................................................................................................˝..........................................<br />
51003<br />
Context too large; recompile using /o switch, with a higher<br />
argument<br />
A state or class contains more KDL than the Optimizer can compile. Try<br />
rerunning the HPO Optimizer using the /O switch. Give a higher argument<br />
to /O than the default.<br />
.........................................................................................................................................................................................................˝..........................................<br />
51004<br />
Too many unique string constants in a context<br />
A state or class contains too many unique string constants. Try breaking up<br />
the state or class into two or more states or classes.<br />
<strong>AionDS</strong> Runtime Errors 1-195