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

IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... 365 2-24 AionDS Messages and Codes MAES address space is unavailable An attempt to BIND with a specific MAES address space failed. The MAES address space has not been started. .........................................................................................................................................................................................................˝.......................................... 392 Program quiesced on node xxxxxxxx, no new users allowed A request to attach another subtask for the program SADS, SAES, or an optimized knowledge base has failed because the program in question has been quiesced through the MONITOR KB. No new users will be allowed in until all active users have finished and the program is reactivated. Contact your AionDS system administrator to resolve this error. .........................................................................................................................................................................................................˝.......................................... 811 Driver and xxxxxxxx versions do not match The version of MAES (node name xxxxxxxx) and the transaction driver are incompatible. .........................................................................................................................................................................................................˝.......................................... 900 Node xxxxxxxx is invalid for LU6.2 connection VTAM node xxxxxxxx is unknown to VTAM. This is produced by the IMS/CPO server program. .........................................................................................................................................................................................................˝.......................................... 902 Node xxxxxxxx is not an LU6.2 node Node xxxxxxxx is one of the possible OS/2 or other communication partners for IMS/CPO. However, the VTAM protocol used during the BIND process was not LU6.2. The attempt to BIND failed. .........................................................................................................................................................................................................˝.......................................... 903 No sessions available for LU6.2 node xxxxxxxx The IMS/CPO function attempted to communicate with BAES or MAES. However, not enough parallel sessions have been defined.

IMS and TSO transaction driver messages .........................................................................................................................................................................................................˝.......................................... 904 Node xxxxxxxx is inactive The IMS/CPO function attempted to BIND to the node xxxxxxxx. However, the node is not active. .........................................................................................................................................................................................................˝.......................................... 905 No sessions for node xxxxxxxx bound An LU6.2 connection between IMS/CPO and MAES (for remote knowledge base) or BAES (for the DL/I data server) failed because no sessions were bound between MAES and the PC. Typically, this indicates a problem in the connection definition on the PC or at the VTAM level. .........................................................................................................................................................................................................˝.......................................... 906 CID for node xxxxxxxx is invalid An active session between IMS/CPO and xxxxxxxx failed causing an invalid conversation ID condition. Typically this will happen if xxxxxxxx is stopped while still processing messages with IMS/CPO. .........................................................................................................................................................................................................˝.......................................... 907 Attempted to free an unowned session for node xxxxxxxx An internal error caused the IMS/CPO function to attempt a release of a VTAM session owned by the VTAM partner. This error should be reported to PLATINUM Technical Support for AionDS. .........................................................................................................................................................................................................˝.......................................... 908 Free session for node xxxxxxxx invalid - bad owner An attempt to free a VTAM session failed. This is an internal error and should be reported to PLATINUM Technical Support for AionDS. Transaction Driver Messages 2-25

IMS <strong>and</strong> TSO transaction driver messages<br />

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

904<br />

Node xxxxxxxx is inactive<br />

The IMS/CPO function attempted to BIND to the node xxxxxxxx.<br />

However, the node is not active.<br />

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

905<br />

No sessions for node xxxxxxxx bound<br />

An LU6.2 connection between IMS/CPO <strong>and</strong> MAES (for remote knowledge<br />

base) or BAES (for the DL/I data server) failed because no sessions were<br />

bound between MAES <strong>and</strong> the PC. Typically, this indicates a problem in the<br />

connection definition on the PC or at the VTAM level.<br />

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

906<br />

CID for node xxxxxxxx is invalid<br />

An active session between IMS/CPO <strong>and</strong> xxxxxxxx failed causing an invalid<br />

conversation ID condition. Typically this will happen if xxxxxxxx is stopped<br />

while still processing messages with IMS/CPO.<br />

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

907<br />

Attempted to free an unowned session for node xxxxxxxx<br />

An internal error caused the IMS/CPO function to attempt a release of a<br />

VTAM session owned by the VTAM partner. This error should be reported<br />

to PLATINUM Technical Support for <strong>AionDS</strong>.<br />

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

908<br />

Free session for node xxxxxxxx invalid - bad owner<br />

An attempt to free a VTAM session failed. This is an internal error <strong>and</strong><br />

should be reported to PLATINUM Technical Support for <strong>AionDS</strong>.<br />

Transaction Driver <strong>Messages</strong> 2-25

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!