AionDS Messages and Codes Guide

AionDS Messages and Codes Guide AionDS Messages and Codes Guide

arti.vub.ac.be
from arti.vub.ac.be More from this publisher
29.06.2013 Views

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

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:

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!