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 .........................................................................................................................................................................................................˝.......................................... 14006 6-48 AionDS Messages and Codes MAESETXR When a consultation terminates, MAESETXR attempts to deallocate any datasets that might have been allocated by the subtask, but not deallocated by the inference engine. These datasets have a consultation-unique identifier (Annn) prefixed to the DD name. If the deallocation fails, this error message is issued with the DD name that MAESETXR failed to process. If a deallocation failure occurs, it can interfere with subsequent consultations because the consultation-unique identifier is reusable. The reason for the deallocation failure is found in the operating system job log for MAES. The deallocation failure is listed as a standard MVS error message. Examine the MVS error message and correct the error condition before trying to run MAES again. .........................................................................................................................................................................................................˝.......................................... 14007 MAESLUNM This log message indicates that the DD statement for MAESLUNM was missing from the JCL stream. MAES requires all potential session partners to be identified before any sessions are established. The dataset associated with the MAESLUNM DD statement is scanned to identify potential session partners. Correct the error and resubmit the MAES JCL. .........................................................................................................................................................................................................˝.......................................... 14008 MAESLUNM MAESLUNM found the ACQUIRE keyword, but the argument is neither YES nor NO. The correct form is ACQUIRE(YES) or ACQUIRE(NO). Correct the MAESLUNM dataset and resubmit the MAES JCL. .........................................................................................................................................................................................................˝.......................................... 14009 MAESLUNM MAESLUNM found the TYPE keyword, but the argument is not a valid selection such as CICS or IMS. Review the MAESLUNM dataset in conjunction with this guidebook and correct any errors before resubmitting the MAES JCL.

MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 14010 MAESLUNM Either the WIN or the MAX keyword was specified, but the TYPE keyword indicates the potential session partner is not an LU6.2 interface with parallel session support. For instance, WIN or MAX is invalid if TYPE(IMS) was specified. Correct the MAESLUNM dataset and resubmit the MAES JCL. .........................................................................................................................................................................................................˝.......................................... 14011 MAESLUNM A potential session partner is being defined, but MAX was not specified for the WIN keyword. MAES needs to know the maximum number of traffic sessions that are supported so that it can maintain the appropriate number of internal control blocks. Correct the MAESLUNM dataset and resubmit the MAES JCL. .........................................................................................................................................................................................................˝.......................................... 14012 MAESLUNM In processing an MAESLUNM specification for a session partner where MAES owns some of the traffic sessions, it was determined that the value from WIN exceeded the maximum number of traffic sessions as specified by MAX. Correct the problem and resubmit the MAES JCL. .........................................................................................................................................................................................................˝.......................................... 14013 MAESLUNM MAES processed the MAESLUNMdataset. The MAESLUNM dataset was either empty or all the entries had an associated error. In either case, correct the problems and resubmit the MAES JCL. .........................................................................................................................................................................................................˝.......................................... 14014 MAESPARM When execute parameter information is received, MAESPARM dynamically links to the MAESPC module which is used to parse the information. However, an error occurred while attempting to LINK to MAESPC. This log message is recorded and MAES terminates. Examine the MVS job log for the MAES job with the error messages which can be used to solve the problem. Usually, the problem is that the module is not in the STEPLIB or MAESLOG Messages 6-49

MAESLOG messages<br />

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

14010<br />

MAESLUNM<br />

Either the WIN or the MAX keyword was specified, but the TYPE keyword<br />

indicates the potential session partner is not an LU6.2 interface with parallel<br />

session support. For instance, WIN or MAX is invalid if TYPE(IMS) was<br />

specified. Correct the MAESLUNM dataset <strong>and</strong> resubmit the MAES JCL.<br />

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

14011<br />

MAESLUNM<br />

A potential session partner is being defined, but MAX was not specified for<br />

the WIN keyword. MAES needs to know the maximum number of traffic<br />

sessions that are supported so that it can maintain the appropriate number of<br />

internal control blocks. Correct the MAESLUNM dataset <strong>and</strong> resubmit the<br />

MAES JCL.<br />

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

14012<br />

MAESLUNM<br />

In processing an MAESLUNM specification for a session partner where<br />

MAES owns some of the traffic sessions, it was determined that the value<br />

from WIN exceeded the maximum number of traffic sessions as specified by<br />

MAX. Correct the problem <strong>and</strong> resubmit the MAES JCL.<br />

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

14013<br />

MAESLUNM<br />

MAES processed the MAESLUNMdataset. The MAESLUNM dataset was<br />

either empty or all the entries had an associated error. In either case, correct<br />

the problems <strong>and</strong> resubmit the MAES JCL.<br />

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

14014<br />

MAESPARM<br />

When execute parameter information is received, MAESPARM dynamically<br />

links to the MAESPC module which is used to parse the information.<br />

However, an error occurred while attempting to LINK to MAESPC. This<br />

log message is recorded <strong>and</strong> MAES terminates. Examine the MVS job log for<br />

the MAES job with the error messages which can be used to solve the<br />

problem. Usually, the problem is that the module is not in the STEPLIB or<br />

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

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!