AionDS Messages and Codes Guide
AionDS Messages and Codes Guide AionDS Messages and Codes Guide
MAES-specific codes MAES-specific codes .........................................................................................................................................................................................................˝.......................................... Overview 5-2 AionDS Messages and Codes The following codes are used by MAES and the transaction drivers to build communication messages. In addition, error codes that can be set as the result of communication, protocol, database, or application errors are contained here. The MAESERRC member of the MACLIB database, provided on the AionDS/CICS and AionDS/IMS distribution tapes, contains this information in machine-readable form. These error codes can be displayed on the user’s terminal as part of transaction driver error messages, in the AionDS system log as part of error and remote database messages, and in the MAESLOG to document message traffic flow between the partner logical unit and MAES. .........................................................................................................................................................................................................˝.......................................... 100 User input message sent to MASES. This message is probably displayed because of a protocol error or possibly an invalid message switch from a user program to the transaction driver. The following codes are the type of user input message sent to MAES: Code number Description 102 User 3270 Data Stream. The input is the input form an AionDS screen. 103 User Field-by-Field. This input is in the form of an FPL .........................................................................................................................................................................................................˝.......................................... 200 Screen output message. This is displayed when a screen is sent to the transaction driver out of sequence. For example, you start an embedded knowledge base by calling AAESFPL and the knowledge base sends a screen (abort of user sourcing screen). Since screens are not allowed in embedded processing, this error code can be displayed. The following codes are the type of screen output message:
Code number Description 202 3270 Data Stream. Normal AionDS screen. 206 ADSMSW requested a message switch. MAES-specific codes 207 Field-by-field unblocked message. The output parameters for an FPL are being sent back. 208 The knowledge base called ADSMOD to set a new IMS MODNAME for the next report to use. .........................................................................................................................................................................................................˝.......................................... 300 A status message was received. The following codes are the type of the status messages: Code number Description 308 Consultation end request. The knowledge base stopped unexpectedly. 309 Timeout on the MAES side. Avoid timing out by increasing the TIME MAESPARM. 310 Maxtask limit reached in MAES. 350 Generic failure in the message protocols. MAES Error Codes 5-3
- 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 ......
- 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: Chapter 5 MAES Error Codes ........
- 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 ..................
- Page 293 and 294: MAESLOG messages ..................
- Page 295 and 296: MAESLOG messages ..................
- Page 297 and 298: MAESLOG messages ..................
- Page 299 and 300: MAESLOG messages Since this error r
- Page 301 and 302: MAESLOG messages ..................
- Page 303 and 304: MAESLOG messages ..................
- Page 305 and 306: MAESLOG messages ..................
- Page 307 and 308: MAESLOG messages ..................
- Page 309 and 310: MAESLOG messages ..................
- Page 311 and 312: MAESLOG messages ..................
- Page 313 and 314: MAESLOG messages ..................
- Page 315 and 316: MAESLOG messages ..................
- Page 317 and 318: MAESLOG messages ..................
- Page 319 and 320: MAESLOG messages ..................
MAES-specific codes<br />
MAES-specific codes<br />
.........................................................................................................................................................................................................˝..........................................<br />
Overview<br />
5-2 <strong>AionDS</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />
The following codes are used by MAES <strong>and</strong> the transaction drivers to build<br />
communication messages. In addition, error codes that can be set as the<br />
result of communication, protocol, database, or application errors are<br />
contained here. The MAESERRC member of the MACLIB database,<br />
provided on the <strong>AionDS</strong>/CICS <strong>and</strong> <strong>AionDS</strong>/IMS distribution tapes, contains<br />
this information in machine-readable form.<br />
These error codes can be displayed on the user’s terminal as part of<br />
transaction driver error messages, in the <strong>AionDS</strong> system log as part of error<br />
<strong>and</strong> remote database messages, <strong>and</strong> in the MAESLOG to document message<br />
traffic flow between the partner logical unit <strong>and</strong> MAES.<br />
.........................................................................................................................................................................................................˝..........................................<br />
100<br />
User input message sent to MASES. This message is probably displayed<br />
because of a protocol error or possibly an invalid message switch from a user<br />
program to the transaction driver. The following codes are the type of user<br />
input message sent to MAES:<br />
Code number Description<br />
102 User 3270 Data Stream. The input is the input form an<br />
<strong>AionDS</strong> screen.<br />
103 User Field-by-Field. This input is in the form of an FPL<br />
.........................................................................................................................................................................................................˝..........................................<br />
200<br />
Screen output message. This is displayed when a screen is sent to the<br />
transaction driver out of sequence. For example, you start an embedded<br />
knowledge base by calling AAESFPL <strong>and</strong> the knowledge base sends a screen<br />
(abort of user sourcing screen). Since screens are not allowed in embedded<br />
processing, this error code can be displayed. The following codes are the type<br />
of screen output message: