AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... 916 2-26 AionDS Messages and Codes COMMREC parameter missing for REMOTE KB request A remote knowledge base request was detected but the COMMREC parameter was missing. The COMMREC parameter describes the MAES node that contains the remote knowledge base and the name of the remote knowledge base. For more information: See the AionDS/IMS Installation and Operation Guide for more information on remote knowledge bases. .........................................................................................................................................................................................................˝.......................................... 3150 Knowledge base name is missing You entered the transaction code and did not specify a knowledge base name or the RUNADS ($ADS) string for a development session. .........................................................................................................................................................................................................˝.......................................... 3151 Request was rejected by the user edit routine A user-written input edit routine rejected the input message. You can override this default message in the input edit routine. .........................................................................................................................................................................................................˝.......................................... 3155 Unable to get the SPA - status xx The conversational version of the AionDS/IMS transaction driver encountered an error when it tried to retrieve the SPA. The value xx indicates the PCBSTATUS code. .........................................................................................................................................................................................................˝.......................................... 3156 SA error - suspend failed - code ccc The AionDS/IMS transaction driver attempted to suspend the consultation but the suspend failed with code ccc. The consultation is terminated. .........................................................................................................................................................................................................˝.......................................... 3157 PCB status xx encountered in module mmmmmmmm An unexpected PCB status code xx was encountered while module mmmmmmmm was executing.
IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... 3158 Report to xxxxxxxx failed - no PCB available A report was formatted and targeted for the xxxxxxxx logical terminal but could not be sent because no alternate I/O PCB or modifiable PCB for the xxxxxxxx logical terminal was found. .........................................................................................................................................................................................................˝.......................................... 3159 xxxx call failed with status ss Call xxxx failed with PCB status code ss. This error can occur when you edit PCBs for logical terminal output. .........................................................................................................................................................................................................˝.......................................... 3160 xxxxxxxx is an unknown destination for output Output targeted for the xxxxxxxx logical terminal could not be sent because no alternate I/O PCB or modifiable PCB could be found. .........................................................................................................................................................................................................˝.......................................... 3161 No program was specified for $EXE option The user attempted to execute an optimized knowledge base using $EXE KBNAME but neglected to specify KBNAME. .........................................................................................................................................................................................................˝.......................................... 3162 The program specified for $EXE was more than 8 bytes The length of an optimized knowledge base name cannot exceed 8 bytes. .........................................................................................................................................................................................................˝.......................................... 3165 Unable to allocate nnn bytes of memory The transaction driver attempted to acquire nnn bytes of memory but was unsuccessful. Increase the region size for the message processing region and try the request again. Transaction Driver Messages 2-27
- 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 and 208: AionDS runtime errors .............
- Page 209 and 210: 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: 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 ......
- Page 259 and 260: CICS/VS exception conditions ......
- 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: MAESLOG messages ..................
- Page 287 and 288: MAESLOG messages ..................
- Page 289 and 290: MAESLOG messages ..................
- Page 291 and 292: MAESLOG messages ..................
IMS <strong>and</strong> TSO transaction driver messages<br />
.........................................................................................................................................................................................................˝..........................................<br />
3158<br />
Report to xxxxxxxx failed - no PCB available<br />
A report was formatted <strong>and</strong> targeted for the xxxxxxxx logical terminal but<br />
could not be sent because no alternate I/O PCB or modifiable PCB for the<br />
xxxxxxxx logical terminal was found.<br />
.........................................................................................................................................................................................................˝..........................................<br />
3159<br />
xxxx call failed with status ss<br />
Call xxxx failed with PCB status code ss. This error can occur when you edit<br />
PCBs for logical terminal output.<br />
.........................................................................................................................................................................................................˝..........................................<br />
3160<br />
xxxxxxxx is an unknown destination for output<br />
Output targeted for the xxxxxxxx logical terminal could not be sent because<br />
no alternate I/O PCB or modifiable PCB could be found.<br />
.........................................................................................................................................................................................................˝..........................................<br />
3161<br />
No program was specified for $EXE option<br />
The user attempted to execute an optimized knowledge base using $EXE<br />
KBNAME but neglected to specify KBNAME.<br />
.........................................................................................................................................................................................................˝..........................................<br />
3162<br />
The program specified for $EXE was more than 8 bytes<br />
The length of an optimized knowledge base name cannot exceed 8 bytes.<br />
.........................................................................................................................................................................................................˝..........................................<br />
3165<br />
Unable to allocate nnn bytes of memory<br />
The transaction driver attempted to acquire nnn bytes of memory but was<br />
unsuccessful. Increase the region size for the message processing region <strong>and</strong><br />
try the request again.<br />
Transaction Driver <strong>Messages</strong> 2-27
Change language