M204.1935: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Template:M204.1935 skeleton}} | {{Template:M204.1935 skeleton}} | ||
<P> | <P> | ||
An attempt has been made to DEFINE or REDEFINE a field with the UNIQUE attribute in a non-[[Transaction | An attempt has been made to DEFINE or REDEFINE a field with the [[Field_design#UNIQUE_and_NON-UNIQUE_attributes|UNIQUE]] attribute in a non-[[Transaction back out|TBO]] file. </P> | ||
<p> | <p> | ||
<b>File manager response:</b> Since TBO is required for the UNIQUE attribute to be used, reset the FRCVOPT and FOPT parameters to make this a TBO file, or do not use the UNIQUE attribute for this field. </p> | <b>File manager response:</b> Since TBO is required for the UNIQUE attribute to be used, reset the <var>[[FRCVOPT parameter|FRCVOPT]]</var> and <var>[[FOPT parameter|FOPT]]</var> parameters to make this a TBO file, or do not use the UNIQUE attribute for this field. </p> | ||
{{Template:M204.1935 footer}} | {{Template:M204.1935 footer}} | ||
<!-- skeleton as it was in pdf/UNIQUE FIELDS ARE NOT ALLOWED IN NON-TBO FILES /--> | <!-- skeleton as it was in pdf/UNIQUE FIELDS ARE NOT ALLOWED IN NON-TBO FILES /--> | ||
Revision as of 23:08, 15 March 2018
M204.1935 UNIQUE fields are not allowed in non-TBO files
An attempt has been made to DEFINE or REDEFINE a field with the UNIQUE attribute in a non-TBO file.
File manager response: Since TBO is required for the UNIQUE attribute to be used, reset the FRCVOPT and FOPT parameters to make this a TBO file, or do not use the UNIQUE attribute for this field.
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 |