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 .........................................................................................................................................................................................................˝.......................................... 14026 6-52 AionDS Messages and Codes MAESINIT The SAESEP version does not match the MAES version. Processing continues. .........................................................................................................................................................................................................˝.......................................... 14500 SAESLOGM Certain external programs that the inference engine calls as functions (remote KB, message switching, etc.) add log messages to the MAESLOG. All these log messages appear under this log message ID. Typically, they reflect errors in processing. The knowledge base receives a return code from the process object. The return code and log message in the MAESLOG can help you solve the problem. .........................................................................................................................................................................................................˝.......................................... 14504 SAESSTIN The checking program, CHECKPRGM, returned a non-zero value in register 15. The user is probably not authorized. The consultation abends with user abend 377. .........................................................................................................................................................................................................˝.......................................... 14502 SAESRUID SAES expects FPL data to be provided by a screen input message type with a subtype of field-by-field. SAES received a screen input message type, but it was not field-by-field data. This log message can be caused by either programming errors in ADSFPL, AAESFPL or DCFPL, or inconsistent levels between these two programs and MAES. .........................................................................................................................................................................................................˝.......................................... 14503 SAESRUID SAES attempts to allocate enough storage to accommodate the FPL input and output data. Not enough memory is available to complete the request. If increasing the REGION parameter on the EXEC statement does not eliminate the problem, it could be the result of a programming error. In this case, report the problem to PLATINUM Technical Support for AionDS and submit the MAESLOG showing all the data traffic.

MAESLOG messages .........................................................................................................................................................................................................˝.......................................... 15000 MAESLGON A VTAM BIND request was received, but the requestor’s name was not found in the internal control blocks formatted from the MAESLUNM file. If the requestor is valid, the MAESLUNM dataset must be upgraded to include the new session partner. .........................................................................................................................................................................................................˝.......................................... 15001 MAESSCIP This log message is produced when the VTAM SCIP exit gets control on an UNBIND request. MAES uses the VTAM conversation ID (CID) as an argument into internal control blocks. If the session was cleaned up before, it produces this log message. Typically, this is not an error situation. .........................................................................................................................................................................................................˝.......................................... 15002 MAESSERV Using a MONITOR knowledge base function, a user requested that a partner session be terminated. This log message indicates that the LU name could not be found in internal control blocks. This represents a programming error and should be reported to PLATINUM Technical Support for AionDS. .........................................................................................................................................................................................................˝.......................................... 15003 MAESSERV Using a MONITOR knowledge base function, a user requested that a partner session be activated. This log message indicates that the LU name could not be found in internal control blocks. This represents a programming error and should be reported to PLATINUM Technical Support for AionDS. MAESLOG Messages 6-53

MAESLOG messages<br />

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

14026<br />

6-52 <strong>AionDS</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong><br />

MAESINIT<br />

The SAESEP version does not match the MAES version. Processing<br />

continues.<br />

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

14500<br />

SAESLOGM<br />

Certain external programs that the inference engine calls as functions (remote<br />

KB, message switching, etc.) add log messages to the MAESLOG. All these<br />

log messages appear under this log message ID. Typically, they reflect errors<br />

in processing. The knowledge base receives a return code from the process<br />

object. The return code <strong>and</strong> log message in the MAESLOG can help you<br />

solve the problem.<br />

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

14504<br />

SAESSTIN<br />

The checking program, CHECKPRGM, returned a non-zero value in register<br />

15. The user is probably not authorized. The consultation abends with user<br />

abend 377.<br />

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

14502<br />

SAESRUID<br />

SAES expects FPL data to be provided by a screen input message type with a<br />

subtype of field-by-field. SAES received a screen input message type, but it<br />

was not field-by-field data. This log message can be caused by either<br />

programming errors in ADSFPL, AAESFPL or DCFPL, or inconsistent levels<br />

between these two programs <strong>and</strong> MAES.<br />

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

14503<br />

SAESRUID<br />

SAES attempts to allocate enough storage to accommodate the FPL input <strong>and</strong><br />

output data. Not enough memory is available to complete the request. If<br />

increasing the REGION parameter on the EXEC statement does not<br />

eliminate the problem, it could be the result of a programming error. In this<br />

case, report the problem to PLATINUM Technical Support for <strong>AionDS</strong> <strong>and</strong><br />

submit the MAESLOG showing all the data traffic.

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!