AionDS Messages and Codes Guide
Share Embed Flag
Download ePaper

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

MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 16002 6-56 AionDS Messages and Codes XAESNCON After an XMS bind was successful, the transaction driver sent a message to MAES that was either invalid or out of sequence. Send the MAESLOG and any other supporting documentation to PLATINUM Technical Support for AionDS. .........................................................................................................................................................................................................˝.......................................... 16003 MAESSECS See log message 16001. This is the reverse of the situation in which an XMS session was established and a transaction driver attempts to establish a VTAM session. .........................................................................................................................................................................................................˝.......................................... 16004 SAESXMGE MAES posted the consultation with a stop request. This typically happens during shutdown or in a situation in which a new consultation is to be started from the same terminal. .........................................................................................................................................................................................................˝.......................................... 16005 SAESXMSE An XMS SEND request completed, but the transaction driver indicated that there was an error. This should be reported with the MAESLOG to PLATINUM Technical Support for AionDS. .........................................................................................................................................................................................................˝.......................................... 16006 XAESNCON After an XMS bind is received, MAES attempts to establish an ENQ for the transaction driver. The ENQ failed. Send the MAESLOG and other supporting material to PLATINUM Technical Support for AionDS. .........................................................................................................................................................................................................˝.......................................... 16007 SAESXMSE An attempt was made to send a message to the transaction driver. However, the transaction driver either failed or a protocol error occurred.

MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 16008 XAESNCON While trying to complete a sequence of protocol messages, the cross memory connection to a transaction driver failed. Typically, this occurs when the transaction driver abends. .........................................................................................................................................................................................................˝.......................................... 16105 SAESXMSE A cross memory services SEND failed. .........................................................................................................................................................................................................˝.......................................... 16107 SAESXMGE A cross memory services GET failed. .........................................................................................................................................................................................................˝.......................................... 17000 SAESAPI An initialize API request was received from the transaction driver but the request failed. Diagnostic information is printed. .........................................................................................................................................................................................................˝.......................................... 17001 SAESAPI A request to initialize a session with the API was received but the request failed. Diagnostic information is printed. MAESLOG Messages 6-57

MAESLOG messages<br />

.........................................................................................................................................................................................................˝..........................................<br />

16008<br />

XAESNCON<br />

While trying to complete a sequence of protocol messages, the cross memory<br />

connection to a transaction driver failed. Typically, this occurs when the<br />

transaction driver abends.<br />

.........................................................................................................................................................................................................˝..........................................<br />

16105<br />

SAESXMSE<br />

A cross memory services SEND failed.<br />

.........................................................................................................................................................................................................˝..........................................<br />

16107<br />

SAESXMGE<br />

A cross memory services GET failed.<br />

.........................................................................................................................................................................................................˝..........................................<br />

17000<br />

SAESAPI<br />

An initialize API request was received from the transaction driver but the<br />

request failed. Diagnostic information is printed.<br />

.........................................................................................................................................................................................................˝..........................................<br />

17001<br />

SAESAPI<br />

A request to initialize a session with the API was received but the request<br />

failed. Diagnostic information is printed.<br />

MAESLOG <strong>Messages</strong> 6-57

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!