M204.0695: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
 
m (add <var>'s)
 
Line 3: Line 3:
Model 204 has detected a binary field that exceeds four bytes in length. The high-order four bytes are stored as the binary number. </P>
Model 204 has detected a binary field that exceeds four bytes in length. The high-order four bytes are stored as the binary number. </P>
<p>
<p>
<b>Response:</b> Correct the FLOD instructions or the source data, and rerun the job. If this FLOD operation updates an existing file, the input stream will have to be edited to account for the previous updates that may have occurred prior
<b>Response:</b> Correct the <var>FLOD</var> instructions or the source data, and rerun the job. If this <var>FLOD</var> operation updates an existing file, the input stream will have to be edited to account for the previous updates that may have occurred prior to the error.  
to the error. </p>
</p>
{{Template:M204.0695 footer}}
{{Template:M204.0695 footer}}
<!-- skeleton as it was in pdf/INVALID BINARY INPUT /-->
<!-- skeleton as it was in pdf/INVALID BINARY INPUT /-->

Latest revision as of 22:49, 27 February 2018

M204.0695  Invalid binary input

Model 204 has detected a binary field that exceeds four bytes in length. The high-order four bytes are stored as the binary number.

Response: Correct the FLOD instructions or the source data, and rerun the job. If this FLOD operation updates an existing file, the input stream will have to be edited to account for the previous updates that may have occurred prior to the error.

Message attributes:

RETCODEO=0Sets online return code
RETCODEB=4Sets batch (single user) return code
CLASS=EError class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter
AUDITERWrites the message with line type ER to the audit trail
COUNTIncrements the error count (ERCNT) parameter

Back to list of messages