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.

CICS/VS exception conditions<br />

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

1206<br />

Invalid “file comm<strong>and</strong> code”.<br />

An invalid or unsupported file comm<strong>and</strong> request was received by the<br />

transaction driver. This error should be reported to PLATINUM Technical<br />

Support for <strong>AionDS</strong>.<br />

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

1207<br />

Invalid length on a variable length parameter.<br />

A request prepared by SAES or an external routine contained a parameter<br />

with an invalid length. Some messages passed to the transaction driver<br />

contain a number of parameters in the message text. Each of these<br />

parameters is of the general form:<br />

where<br />

length parm_flag data<br />

length 2-byte length field<br />

parm_flag one-byte parameter flag<br />

data data associated with the parameter<br />

This error is issued if the length is zero, the length is negative, or the length is<br />

greater than the remainder of the message.<br />

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

1208<br />

Too many parameters in the request.<br />

Given the general format of some requests as shown in message 1207, if the<br />

transaction driver processes the message <strong>and</strong> finds the information needed to<br />

complete the request before processing all the parameters in the message, it<br />

assumes that the message is improperly coded <strong>and</strong> produces status 1208.<br />

This condition can happen if SAES or a user external routine erroneously<br />

duplicates parameters in the message or includes information not needed for<br />

the request type.<br />

CICS/VS Exception Conditions 3-9

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

Saved successfully!

Ooh no, something went wrong!