M204.2122: Difference between revisions
(Automatically generated page update) |
m (add <var>'s) |
||
| Line 2: | Line 2: | ||
<P> | <P> | ||
During a REDEFINE to AT-MOST-ONE or EXACTLY-ONE, a violation of the AT-MOST-ONE or EXACTLY-ONE Field-Level Constraint was discovered in the file. The error message indicates the field name and record number that contain more than one occurrence. All | During a <var>REDEFINE</var> to <var>AT-MOST-ONE</var> or <var>EXACTLY-ONE</var>, a violation of the <var>AT-MOST-ONE</var> or <var>EXACTLY-ONE</var> Field-Level Constraint was discovered in the file. The error message indicates the field name and record number that contain more than one occurrence. All | ||
such violations within the file for the field to be redefined are reported during REDEFINE processing. </P> | such violations within the file for the field to be redefined are reported during <var>REDEFINE</var> processing. </P> | ||
<P> | <P> | ||
The REDEFINE fails, undoing any changes it might have made in the process of AT-MOST-ONE or EXACTLY-ONE verification. </P> | The <var>REDEFINE</var> fails, undoing any changes it might have made in the process of <var>AT-MOST-ONE</var> or <var>EXACTLY-ONE</var> verification. </P> | ||
<p> | <p> | ||
<b>File manager response:</b> Using information from the above message and an understanding of the data and application this file represents, update the file to remove all but one occurrence of the field in the record(s) | <b>File manager response:</b> Using information from the above message and an understanding of the data and application this file represents, update the file to remove all but one occurrence of the field in the record(s) | ||
identified. Once the file is cleared of all pre-existing AT-MOST-ONE and EXACTLY-ONE violations, the REDEFINE of the field to AT-MOST-ONE or EXACTLY-ONE will complete successfully. | identified. Once the file is cleared of all pre-existing <var>AT-MOST-ONE</var> and <var>EXACTLY-ONE</var> violations, the <var>REDEFINE</var> of the field to <var>AT-MOST-ONE</var> or <var>EXACTLY-ONE</var> will complete successfully. | ||
</p> | </p> | ||
{{Template:M204.2122 footer}} | {{Template:M204.2122 footer}} | ||
<!-- skeleton as it was in pdf/AT-MOST-ONE CONSTRAINT VIOLATION FOR FIELD fieldname IN RECORD recordnumber /--> | <!-- skeleton as it was in pdf/AT-MOST-ONE CONSTRAINT VIOLATION FOR FIELD fieldname IN RECORD recordnumber /--> | ||
Latest revision as of 22:31, 15 March 2018
M204.2122 token constraint violation for field token2 in record token3
During a REDEFINE to AT-MOST-ONE or EXACTLY-ONE, a violation of the AT-MOST-ONE or EXACTLY-ONE Field-Level Constraint was discovered in the file. The error message indicates the field name and record number that contain more than one occurrence. All such violations within the file for the field to be redefined are reported during REDEFINE processing.
The REDEFINE fails, undoing any changes it might have made in the process of AT-MOST-ONE or EXACTLY-ONE verification.
File manager response: Using information from the above message and an understanding of the data and application this file represents, update the file to remove all but one occurrence of the field in the record(s) identified. Once the file is cleared of all pre-existing AT-MOST-ONE and EXACTLY-ONE violations, the REDEFINE of the field to AT-MOST-ONE or EXACTLY-ONE will complete successfully.
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 |