M204.0202: Difference between revisions
Jump to navigation
Jump to search
Automatically generated page update |
m add <var>s |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Template:M204.0202 skeleton}} | {{Template:M204.0202 skeleton}} | ||
<P> | <P> | ||
In a | In a <var>File Records</var> statement, <var class="term">fieldName</var> is a <var>NON-KEY</var>, <var>NON-ORDERED</var>, or <var>VISIBLE</var> field in the file (or in at least one file within a group). <var class="term">fieldName</var> must be a <var>KEY</var> (or <var>ORDERED</var>) <var>INVISIBLE</var> field. </P> | ||
<p> | <p> | ||
<b>Response:</b> Correct the statement and retry. </p> | <b>Response:</b> Correct the statement, and retry. | ||
</p> | |||
{{Template:M204.0202 footer}} | {{Template:M204.0202 footer}} | ||
<!-- skeleton as it was in pdf/FILE RECORDS REQUIRES EITHER AN INVISIBLE,KEY OR INVISIBLE ORDERED FIELD. FIELD = fieldname /--> | <!-- skeleton as it was in pdf/FILE RECORDS REQUIRES EITHER AN INVISIBLE,KEY OR INVISIBLE ORDERED FIELD. FIELD = fieldname /--> | ||
Latest revision as of 14:41, 19 June 2018
M204.0202 File records requires either an INVISIBLE, KEY or INVISIBLE, ORDERED field: field = fieldName
In a File Records statement, fieldName is a NON-KEY, NON-ORDERED, or VISIBLE field in the file (or in at least one file within a group). fieldName must be a KEY (or ORDERED) INVISIBLE field.
Response: Correct the statement, and retry.
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 |
| ECHO | Displays the line that caused the error |