M204.1933: Difference between revisions
(Automatically generated page update) |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Template:M204.1933 skeleton}} | {{Template:M204.1933 skeleton}} | ||
<P> | <P> | ||
A uniqueness violation has occurred during processing of a STORE RECORD or IFBREC in a non-TBO file. This can occur only if a file containing unique fields had [[Transaction back out|TBO]] disabled by a RESET command. The record being stored | A uniqueness violation has occurred during processing of a <var>[[Data_maintenance#STORE_RECORD_statement|STORE RECORD]]</var> or <var>[[IFBREC_(HLI_function)|IFBREC]]</var> in a non-TBO file. This can occur only if a file containing unique fields had [[Transaction back out|TBO]] disabled by a <var>[[RESET command|RESET]]</var> command. The record being stored | ||
will remain in table B and indexing for fields already stored will remain in tables C and D. However, the record is logically deleted. If an ON FIELD CONSTRAINT CONFLICT unit exists for the request, it will be invoked. Otherwise, the request will be | will remain in table B and indexing for fields already stored will remain in tables C and D. However, the record is logically deleted. If an ON FIELD CONSTRAINT CONFLICT unit exists for the request, it will be invoked. Otherwise, the request will be | ||
canceled. </P> | canceled. </P> | ||
<p> | <p> | ||
<b>Response:</b> If no <code>ON FCC</code> exists for the request, the message [[M204.1702]] | <b>Response:</b> If no <code>ON FCC</code> exists for the request, the Uniqueness violation message [[M204.1702]] will have already been issued. From within an <code>ON FCC</code>, the $UPDSTAT, $UPDREC, $UNQREC, $UPDFLD, | ||
$UPDVAL, $UPDFILE, and $UPDSTMT functions can be used to acquire information about the conflict that occurred. Decisions about how to handle uniqueness conflicts should be made on an application by application basis. </p> | $UPDVAL, $UPDFILE, and $UPDSTMT [[SOUL $functions]] can be used to acquire information about the conflict that occurred. Decisions about how to handle uniqueness conflicts should be made on an application by application basis. </p> | ||
{{Template:M204.1933 footer}} | {{Template:M204.1933 footer}} | ||
<!-- skeleton as it was in pdf/UNIQUENESS VIOLATION DURING STORE RECORD IN A NON-TBO FILE /--> | <!-- skeleton as it was in pdf/UNIQUENESS VIOLATION DURING STORE RECORD IN A NON-TBO FILE /--> | ||
Revision as of 01:24, 13 March 2018
M204.1933 Uniqueness violation during Store Record in a non-TBO file
A uniqueness violation has occurred during processing of a STORE RECORD or IFBREC in a non-TBO file. This can occur only if a file containing unique fields had TBO disabled by a RESET command. The record being stored will remain in table B and indexing for fields already stored will remain in tables C and D. However, the record is logically deleted. If an ON FIELD CONSTRAINT CONFLICT unit exists for the request, it will be invoked. Otherwise, the request will be canceled.
Response: If no ON FCC exists for the request, the Uniqueness violation message M204.1702 will have already been issued. From within an ON FCC, the $UPDSTAT, $UPDREC, $UNQREC, $UPDFLD,
$UPDVAL, $UPDFILE, and $UPDSTMT SOUL $functions can be used to acquire information about the conflict that occurred. Decisions about how to handle uniqueness conflicts should be made on an application by application basis.
Message attributes:
| RETCODEO=24 | Sets online return code |
|---|---|
| RETCODEB=24 | 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 |
| SAVE | Saves the message in the VIEW ERRORS table |