M204.2414: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
m (add <var>'s) |
||
Line 2: | Line 2: | ||
<P> | <P> | ||
An IFFETCH call specified an edit specification of J(n), L(n), or M(n), which requires truncation or padding on the left, and the field type was pure or mixed DBCS, and the field value's length was different from the length | An <var>IFFETCH</var> call specified an edit specification of J(n), L(n), or M(n), which requires truncation or padding on the left, and the field type was pure or mixed DBCS, and the field value's length was different from the length | ||
specified in the edit specification. DBCS fields can be truncated but not padded on the right.</P> | specified in the edit specification. DBCS fields can be truncated but not padded on the right.</P> | ||
<p> | <p> |
Latest revision as of 17:23, 19 March 2018
M204.2414 DBCS values cannot be truncated or padded on the left
An IFFETCH call specified an edit specification of J(n), L(n), or M(n), which requires truncation or padding on the left, and the field type was pure or mixed DBCS, and the field value's length was different from the length specified in the edit specification. DBCS fields can be truncated but not padded on the right.
Response: Correct the program.
Message attributes:
RETCODEO=0 | Sets online return code |
---|---|
RETCODEB=4 | Sets batch (single user) return code |
CLASS=E | Error class; the message can be suppressed with the X'04' bit setting of the MSGCTL parameter |
AUDITER | Writes the message with line type ER to the audit trail |
COUNT | Increments the error count (ERCNT) parameter |