M204.1933 - Revision history

ELowell at 22:47, 15 March 2018

2018-03-15T22:47:00Z

← Older revision		Revision as of 22:47, 15 March 2018
Line 5:		Line 5:
	canceled. </P>		canceled. </P>
	<p>		<p>
	<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,		<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 [[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>		$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 /-->

ELowell at 01:24, 13 March 2018

2018-03-13T01:24:34Z

← Older revision		Revision as of 01:24, 13 March 2018
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]] ~~<code>Uniqueness violation detected for <i>token0</i> = <i>token2</i> in file <i>fileName</i></code>~~ will have already been issued. From within an <code>ON FCC</code>, the $UPDSTAT, $UPDREC, $UNQREC, $UPDFLD,		<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 /-->

DmeWiccan: Automatically generated page update

2018-03-07T17:35:12Z

Automatically generated page update

New page

{{Template:M204.1933 skeleton}}

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
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 <code>ON FCC</code> exists for the request, the message [[M204.1702]] <code>Uniqueness violation detected for token0 = token2 in file fileName</code> 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. 
{{Template:M204.1933 footer}}