JAL: add `'s`

2018-03-15T22:17:51Z

add <var>'s

DmeWiccan: Automatically generated page update

2018-03-14T03:34:39Z

Automatically generated page update

New page

{{Template:M204.2119 skeleton}}


An attempt was made to store, add, or insert a second occurrence of an AT-MOST-ONE or EXACTLY-ONE field in the record indicated. The second occurrence, also indicated in the message, is not added/inserted in Table B, or in
any index (if applicable). The requested update is not performed. This message is issued only when no <code>ON FIELD CONSTRAINT CONFLICT</code> unit exists for the request. 

If the failed request was from SOUL, the request is canceled and its active transaction, if any, is backed out. For failed requests from Host Language Interface, the message is accompanied by Return
Code 202 (without request cancellation). For failed requests during Fastload (FLOD or FILELOAD), Fastload continues, but the file is marked "logically inconsistent" (see the FISTAT parameter). 

Response: SOUL procedures that update AT-MOST-ONE or EXACTLY-ONE fields should always contain ON FCC units to handle AT-MOST-ONE conflicts ($UPDSTAT code 2) when they occur. Similarly, Host Language Interface programs
should code routines to handle AT-MOST-ONE violations, as indicated by the Return Code 202. Fastload must be corrected, following a RESET of FISTAT (see below), to properly load AT-MOST-ONE fields. 

File manager response: From SOUL or Host Language Interface, no response is necessary. 

From Fastload (FLOD or FILELOAD), the FISTAT parameter will have been set to X'40', "logically inconsistent", as a warning that the state of file integrity is questionable, depending on whether or not the failed
request "cascaded" invalid Fastload decisions and results. Consult with the user to determine the logical consistency ramifications of the particular Fastload in question. RESET FISTAT to X'00' once a plan for corrective action, if any,
is determined. 
{{Template:M204.2119 footer}}

← Older revision		Revision as of 22:17, 15 March 2018
Line 2:		Line 2:

	<P>		<P>
	An attempt was made to store, add, or insert a second occurrence of an AT-MOST-ONE or EXACTLY-ONE field in the record indicated. The second occurrence, also indicated in the message, is not added/inserted in Table B, or in		An attempt was made to store, add, or insert a second occurrence of an <var>AT-MOST-ONE</var> or <var>EXACTLY-ONE</var> field in the record indicated. The second occurrence, also indicated in the message, is not added/inserted in Table B, or in
	any index (if applicable). The requested update is not performed. This message is issued only when no <code>ON FIELD CONSTRAINT CONFLICT</code> unit exists for the request. </P>		any index (if applicable). The requested update is not performed. This message is issued only when no <code>ON FIELD CONSTRAINT CONFLICT</code> unit exists for the request. </P>
	<P>		<P>
	If the failed request was from SOUL, the request is canceled and its active transaction, if any, is backed out. For failed requests from Host Language Interface, the message is accompanied by Return		If the failed request was from SOUL, the request is canceled and its active transaction, if any, is backed out. For failed requests from Host Language Interface, the message is accompanied by Return
	Code 202 (without request cancellation). For failed requests during Fastload (FLOD or FILELOAD), Fastload continues, but the file is marked "logically inconsistent" (see the FISTAT parameter). </P>		Code 202 (without request cancellation). For failed requests during Fastload (<var>FLOD</var> or <var>FILELOAD</var>), Fastload continues, but the file is marked "logically inconsistent" (see the <var>[[FISTAT parameter\|FISTAT]]</var> parameter). </P>
	<p>		<p>
	<b>Response:</b> SOUL procedures that update AT-MOST-ONE or EXACTLY-ONE fields should always contain ON FCC units to handle AT-MOST-ONE conflicts ($~~UPDSTAT~~ code 2) when they occur. Similarly, Host Language Interface programs		<b>Response:</b> SOUL procedures that update <var>AT-MOST-ONE</var> or <var>EXACTLY-ONE</var> fields should always contain <var>On FCC</var> units to handle <var>AT-MOST-ONE</var> conflicts (<var>$Updstat</var> code 2) when they occur. Similarly, Host Language Interface programs
	should code routines to handle AT-MOST-ONE violations, as indicated by the Return Code 202. Fastload must be corrected, following a RESET of FISTAT (see below), to properly load AT-MOST-ONE fields. </p>		should code routines to handle <var>AT-MOST-ONE</var> violations, as indicated by the Return Code 202. Fastload must be corrected, following a <var>RESET</var> of <var>FISTAT</var> (see below), to properly load <var>AT-MOST-ONE</var> fields. </p>
	<p>		<p>
	<b>File manager response:</b> From SOUL or Host Language Interface, no response is necessary. </p>		<b>File manager response:</b> From SOUL or Host Language Interface, no response is necessary. </p>
	<P>		<P>
	From Fastload (~~FLOD~~ or FILELOAD), the FISTAT parameter will have been set to X'40', "logically inconsistent", as a warning that the state of file integrity is questionable, depending on whether or not the failed		From Fastload (<var>FLOAD</var> or <var>FILELOAD</var>), the <var>FISTAT</var> parameter will have been set to X'40', "logically inconsistent," as a warning that the state of file integrity is questionable, depending on whether or not the failed
	request "cascaded" invalid Fastload decisions and results. Consult with the user to determine the logical consistency ramifications of the particular Fastload in question. ~~RESET~~ FISTAT to X'00' once a plan for corrective action, if any,		request "cascaded" invalid Fastload decisions and results. </p>
	is determined. </P>		<p>
			Consult with the user to determine the logical consistency ramifications of the particular Fastload in question. Reset <var>FISTAT</var> to X'00' once a plan for corrective action, if any, is determined.
			</P>
	{{Template:M204.2119 footer}}		{{Template:M204.2119 footer}}
	<!-- skeleton as it was in pdf/AT-MOST/EXACTLY-ONE CONSTRAINT VIOLATION IN RECORD recordnumber, FIELD IGNORED: fieldname = value /-->		<!-- skeleton as it was in pdf/AT-MOST/EXACTLY-ONE CONSTRAINT VIOLATION IN RECORD recordnumber, FIELD IGNORED: fieldname = value /-->

M204.2119 - Revision history

JAL: add 's

DmeWiccan: Automatically generated page update

JAL: add `'s`