M204.1702: Difference between revisions
(Automatically generated page update) |
m (add link) |
||
| Line 1: | Line 1: | ||
{{Template:M204.1702 skeleton}} | {{Template:M204.1702 skeleton}} | ||
<P> | <P> | ||
The request has attempted to add an occurrence of a fieldname=value pair for a unique field (via | The request has attempted to add an occurrence of a fieldname=value pair for a unique field (via <var>Add</var>, <var>Insert</var>, <var>Change</var>, or <var>Store Record</var>) and that fieldname=value pair already exits in another record in the file. The requested update will not be performed. </p> | ||
<p> | <p> | ||
This message is issued only when no | This message is issued only when no <var>[[On units|On Field Constraint Conflict unit]]</var> exists for the request. The request will be canceled and its active transaction (if any) will be backed out. </P> | ||
<p> | <p> | ||
<b>Response:</b> Procedures that update unique fields should always contain | <b>Response:</b> Procedures that update unique fields should always contain <var>On Fcc</var> units to handle uniqueness conflicts when they occur. Decisions about how to handle uniqueness conflicts should be made on an application by application basis. | ||
basis. </p> | </p> | ||
{{Template:M204.1702 footer}} | {{Template:M204.1702 footer}} | ||
<!-- skeleton as it was in pdf/UNIQUENESS VIOLATION DETECTED FOR fieldname = value IN FILE filename /--> | <!-- skeleton as it was in pdf/UNIQUENESS VIOLATION DETECTED FOR fieldname = value IN FILE filename /--> | ||
Latest revision as of 16:16, 12 March 2018
M204.1702 Uniqueness violation detected for token = token2 in file fileName
The request has attempted to add an occurrence of a fieldname=value pair for a unique field (via Add, Insert, Change, or Store Record) and that fieldname=value pair already exits in another record in the file. The requested update will not be performed.
This message is issued only when no On Field Constraint Conflict unit exists for the request. The request will be canceled and its active transaction (if any) will be backed out.
Response: Procedures that update unique fields should always contain On Fcc units to handle uniqueness conflicts when they occur. Decisions about how to handle uniqueness conflicts should be made on an application by application basis.
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 |