JAL: add link

2018-03-16T17:53:29Z

add link

← Older revision		Revision as of 17:53, 16 March 2018
Line 2:		Line 2:

	<P>		<P>
	An attempt was made to store invalid data into a BINARY field in a ~~NUMERIC VALIDATION~~ file. For ~~User Language~~ or Host Language Interface, the request is canceled following the above message; the transaction is backed out,		An attempt was made to store invalid data into a <var>BINARY</var> field in a [[Field attributes#File model feature\|Numeric Validation]] file. For SOUL or Host Language Interface, the request is canceled following the above message; the transaction is backed out,
	as TBO is a ~~NUMERIC VALIDATION~~ requirement. For Fastload (FLOD or FILELOAD), the above message is issued without cancellation, the field is dropped and the file is marked "logically inconsistent." </P>		as TBO is a Numeric Validation requirement. For Fastload (<var>FLOD</var> or <var>FILELOAD</var>), the above message is issued without cancellation, the field is dropped and the file is marked "logically inconsistent." </P>
	<p>		<p>
	<b>Response:</b> For SOUL or Host Language Interface, correct the input data to be a valid <var>BINARY</var> number, and resubmit the transaction. </p>		<b>Response:</b> For SOUL or Host Language Interface, correct the input data to be a valid <var>BINARY</var> number, and resubmit the transaction. </p>
	<P>		<P>
	For Fastload (FLOD or FILELOAD), make note of all ~~NUMERIC VALIDATION~~ violations for the run, and construct one or more updates to the file that supply the correct BINARY data values. The File Manager (see below) must		For Fastload (<var>FLOD</var> or <var>FILELOAD</var>), make note of all Numeric Validation violations for the run, and construct one or more updates to the file that supply the correct <var>BINARY</var> data values. The File Manager (see below) must <var>RESET</var> the <var>FISTAT</var> parameter to X'00' prior to running the correctional updates. If the Fastload was written such that decisions were made based on an anticipated <var>BINARY</var> field update, the entire Fastload should be re-run after correcting the invalid
	RESET the FISTAT parameter to X'00' prior to running the correctional updates. If the Fastload was written such that decisions were made based on an anticipated BINARY field update, the entire Fastload should be re-run after correcting the invalid		<var>BINARY</var> field input — this type of error situation is the reason behind the "logically inconsistent" warning. </P>
	BINARY field input — this type of error situation is the reason behind the "logically inconsistent" warning. </P>
	<p>		<p>
	<b>File manager response:</b> For SOUL or Host Language Interface, no response is necessary. </p>		<b>File manager response:</b> For SOUL or Host Language Interface, no response is necessary. </p>
	<P>		<P>
	For Fastload (FLOD or FILELOAD), ~~RESET~~ the FISTAT parameter to X'00' once the user is ready to submit correct BINARY data input. FISTAT has been set to X'40' as a reminder that the current state of the file may be		For Fastload (<var>FLOD</var> or <var>FILELOAD</var>), reset the <var>FISTAT</var> parameter to X'00' once the user is ready to submit correct <var>BINARY</var> data input. <var>FISTAT</var> has been set to X'40' as a reminder that the current state of the file may be
	"logically inconsistent," depending on how the Fastload was written. </P>		"logically inconsistent," depending on how the Fastload was written.
			</P>
	{{Template:M204.2123 footer}}		{{Template:M204.2123 footer}}
	<!-- skeleton as it was in pdf/VALUE SPECIFIED VIOLATES BINARY DATA TYPE VALIDATION IN RECORD recordnumber, FIELD IGNORED: fieldname = value /-->		<!-- skeleton as it was in pdf/VALUE SPECIFIED VIOLATES BINARY DATA TYPE VALIDATION IN RECORD recordnumber, FIELD IGNORED: fieldname = value /-->

DmeWiccan: Automatically generated page update

2018-03-14T03:34:49Z

Automatically generated page update

New page

{{Template:M204.2123 skeleton}}


An attempt was made to store invalid data into a BINARY field in a NUMERIC VALIDATION file. For User Language or Host Language Interface, the request is canceled following the above message; the transaction is backed out,
as TBO is a NUMERIC VALIDATION requirement. For Fastload (FLOD or FILELOAD), the above message is issued without cancellation, the field is dropped and the file is marked "logically inconsistent." 

Response: For SOUL or Host Language Interface, correct the input data to be a valid <var>BINARY</var> number, and resubmit the transaction. 

For Fastload (FLOD or FILELOAD), make note of all NUMERIC VALIDATION violations for the run, and construct one or more updates to the file that supply the correct BINARY data values. The File Manager (see below) must
RESET the FISTAT parameter to X'00' prior to running the correctional updates. If the Fastload was written such that decisions were made based on an anticipated BINARY field update, the entire Fastload should be re-run after correcting the invalid
BINARY field input — this type of error situation is the reason behind the "logically inconsistent" warning. 

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

For Fastload (FLOD or FILELOAD), RESET the FISTAT parameter to X'00' once the user is ready to submit correct BINARY data input. FISTAT has been set to X'40' as a reminder that the current state of the file may be
"logically inconsistent," depending on how the Fastload was written. 
{{Template:M204.2123 footer}}

M204.2123 - Revision history

JAL: add link

DmeWiccan: Automatically generated page update