29.06.2013 Views

AionDS Messages and Codes Guide

AionDS Messages and Codes Guide

AionDS Messages and Codes Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Version 6.0-style messages (MSG600=YES)<br />

CICS transaction driver messages<br />

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

Overview<br />

When the MSG600 parameter is set to YES, the transaction driver displays<br />

messages on the user’s terminal using the format provided in Version 6.0. It<br />

is recommended that you set MSG600=NO unless you have an unknown<br />

message h<strong>and</strong>ler exit routine that expects error messages to be formatted as<br />

they were in Version 6.0. The Version 6.0 message format is described as<br />

follows:<br />

msg_no routine label text<br />

msg_no 2-digit message number<br />

routine name of the routine generating the message (1 to 8<br />

characters)<br />

label name of the routine in the transaction driver that<br />

created the error message (1 to 8 characters)<br />

text variable error message text<br />

The Version 6.0-style CICS transaction driver messages are listed below in<br />

numeric order.<br />

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

01<br />

xxxxxxxx xxxxxxxx COMMAND cccccccc FAILED - CONDITION<br />

yyyyyyyy<br />

where<br />

cccccccc CICS comm<strong>and</strong> that failed<br />

yyyyyyyy error condition<br />

This message is created when a CICS comm<strong>and</strong> error condition is detected.<br />

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

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

Saved successfully!

Ooh no, something went wrong!