FLOD command - Revision history

JAL: add link to Fast/Reload

2017-05-09T18:19:20Z

add link to Fast/Reload

← Older revision		Revision as of 18:19, 9 May 2017
Line 46:		Line 46:
	==Usage notes==		==Usage notes==
	<p>		<p>
	The <var>FLOD</var> command invokes the File Load (FLOD) utility. Use this command when performing a multistep File Load procedure. The <var>FILELOAD</var> command invokes a single-step File Load procedure.</p>		The <var>FLOD</var> command ordinarily invokes the File Load (FLOD) utility. Use this command when performing a multistep File Load procedure. The <var>[[FILELOAD command\|FILELOAD]]</var> command ordinarily invokes a single-step File Load procedure. </p>
			<p class="note"><b>Note:</b> For a site that is authorized for <var class="product">[[Fast/Reload]]</var>, the <var>FLOD</var> and <var>FILELOAD</var> commands are syntactically unchanged but invoke <var class="product">Fast/Reload</var>, which compiles and executes the <var>FLOD</var> and <var>FILELOAD</var> programs.</p>
	<p>		<p>
	<var>FLOD</var> signals the start of a File Load program that consists of special statements that load data from a sequential file into a <var class="product">Model 204</var> file.</p>		<var>FLOD</var> signals the start of a File Load program that consists of special statements that load data from a sequential file into a <var class="product">Model 204</var> file.</p>

JAL: misc formatting

2017-05-09T16:33:55Z

misc formatting

Show changes

ELowell: /* Deferred update data sets */

2016-02-03T18:02:22Z

Deferred update data sets

← Older revision		Revision as of 18:02, 3 February 2016
Line 59:		Line 59:
	<p>The number of job steps in the entire File Load process depends on the attributes of the fields being updated and the number of deferred update data sets specified in the JCL or on the OPEN command issued immediately before the FLOD command.</p>		<p>The number of job steps in the entire File Load process depends on the attributes of the fields being updated and the number of deferred update data sets specified in the JCL or on the OPEN command issued immediately before the FLOD command.</p>
	====Deferred update data sets====		====Deferred update data sets====
	<p>The TAPEI data set contains the data to be loaded into the <var class="product">Model 204</var> file by the File Load program. The File Load program automatically defers updates to the index and writes the updates to the deferred update data set or data sets. It might be necessary to provide a fixed-length deferred update data set, a variable-length deferred update data set, or both. For information on deferred update data sets, ~~refer to the <var class="book">Rocket Model 204 File Manager's Guide</var>~~.</p>		<p>The TAPEI data set contains the data to be loaded into the <var class="product">Model 204</var> file by the File Load program. The File Load program automatically defers updates to the index and writes the updates to the deferred update data set or data sets. It might be necessary to provide a fixed-length deferred update data set, a variable-length deferred update data set, or both. For information on deferred update data sets, see [[Deferred update feature#Types of deferred update data sets\|Types of deferred update data sets]].</p>
	<p>The default file name of the fixed-length deferred update data set during the first phase is TAPE2. Only hashed index updates (KEY and NUMERIC RANGE fields) can be written to the fixed-length deferred update data set. </p>
			<p>The default file name of the fixed-length deferred update data set during the first phase is TAPE2. Only hashed index updates (KEY and NUMERIC RANGE fields) can be written to the fixed-length deferred update data set.</p>

	<p>The default file name of the variable-length deferred update data set during the first phase is TAPE3. Either hashed index updates (KEY and NUMERIC RANGE fields) or Ordered Index updates (ORDERED fields) can be written to the variable-length deferred update data set. If ORDERED fields are updated by the File Load program, there must be a variable-length deferred update data set supplied in the JCL or EXEC of the first-phase step.</p>		<p>The default file name of the variable-length deferred update data set during the first phase is TAPE3. Either hashed index updates (KEY and NUMERIC RANGE fields) or Ordered Index updates (ORDERED fields) can be written to the variable-length deferred update data set. If ORDERED fields are updated by the File Load program, there must be a variable-length deferred update data set supplied in the JCL or EXEC of the first-phase step.</p>

	<p>The default file names of TAPE2 and TAPE3 can be overridden by specifying the appropriate file name or names on the OPEN command issued before the FLOD command. </p>		<p>The default file names of TAPE2 and TAPE3 can be overridden by specifying the appropriate file name or names on the OPEN command issued before the FLOD command. </p>
	<p>Each deferred update data set must be sorted, then processed by <var class="product">Model 204</var> using the Z command. Input to the Z command comes from the data set associated with the SORT5 DD statement, FILEDEF, or DLBL. If any FRV fields were updated during the first phase of the file load, the Z command that processes the hashed index updates places fixed-length FRV deferred updates in the data set associated with the TAPE5 DD statement, FILEDEF, or DLBL. If all the index updates, both hashed and ordered, have been deferred to the variable-length data set, then the Z command that processes the variable-length data set also produces the FRV deferred update data set. Otherwise, the Z command that processes the fixed-length deferred update data set produces the FRV deferred update data set. </p>		<p><b>Z command</b></p>
			<p>Each deferred update data set must be sorted, then processed by <var class="product">Model 204</var> using the Z command. Input to the Z command comes from the data set associated with the SORT5 DD statement, FILEDEF, or DLBL. If any FRV fields were updated during the first phase of the file load, the Z command that processes the hashed index updates places fixed-length FRV deferred updates in the data set associated with the TAPE5 DD statement, FILEDEF, or DLBL.</p>
			<p>If all the index updates, both hashed and ordered, have been deferred to the variable-length data set, then the Z command that processes the variable-length data set also produces the FRV deferred update data set. Otherwise, the Z command that processes the fixed-length deferred update data set produces the FRV deferred update data set.</p>
			<p><b>Combinations of deferred update data sets</b></p>
	<p>The following discussion explains the consequences of specifying different combinations of deferred update data sets: </p>		<p>The following discussion explains the consequences of specifying different combinations of deferred update data sets: </p>
	<ul>		<ul>
Line 77:		Line 83:
	<p>FLOD with one fixed length deferred update data set - Defer only hashed index updates. No Ordered Index fields can be updated. In the JCL or EXEC for the FLOD run, only TAPE2 is specified with a fixed-length record format. Do not specify TAPE3. If an Ordered Index field is updated, an error message is issued and the FLOD program is ended.</p>		<p>FLOD with one fixed length deferred update data set - Defer only hashed index updates. No Ordered Index fields can be updated. In the JCL or EXEC for the FLOD run, only TAPE2 is specified with a fixed-length record format. Do not specify TAPE3. If an Ordered Index field is updated, an error message is issued and the FLOD program is ended.</p>
	<p>The default names TAPE2 or TAPE3 can be overridden by the OPEN command. </p>		<p>The default names TAPE2 or TAPE3 can be overridden by the OPEN command. </p>
	</li>		</li>
	</ul>		</ul>
	<p>For more information, see the File management topics on the [[File Load utility: FLOD and FILELOAD commands]], [[Deferred update feature\|deferred update feature]], and the [[Z command]].</p>		<p>For more information, see the File management topics on the [[File Load utility: FLOD and FILELOAD commands]], [[Deferred update feature\|deferred update feature]], and the [[Z command]].</p>

ELowell at 22:55, 12 December 2013

2013-12-12T22:55:13Z

← Older revision		Revision as of 22:55, 12 December 2013
Line 79:		Line 79:
	</li>		</li>
	</ul>		</ul>
	<p>For more information, see the File management topics on the [[~~File_Load_Utility:_FLOD_and_FILELOAD_commands\|~~File Load utility: FLOD and FILELOAD commands]], [[~~Deferred_Update_Feature~~\|deferred update feature]], and the [[~~Z_command\|~~Z command]].</p>		<p>For more information, see the File management topics on the [[File Load utility: FLOD and FILELOAD commands]], [[Deferred update feature\|deferred update feature]], and the [[Z command]].</p>

	====FLOD exit feature====		====FLOD exit feature====

ELowell at 19:46, 12 December 2013

2013-12-12T19:46:01Z

← Older revision		Revision as of 19:46, 12 December 2013
Line 82:		Line 82:

	====FLOD exit feature====		====FLOD exit feature====
	<p>The <var class="product">Model 204</var> FLOD exit feature allows for modification of the record image on which the FLOD (or FILELOAD) command acts. With the FLOD exit feature you can create a COBOL or Assembler program to modify the image records. The FLOD exit feature enables the use of multiple input files for FLOD processing. The exit is modeled on SORT exits, similar to the E15 sort exit. See [[~~FLOD_Exits\|~~FLOD exits]] for details.</p>		<p>The <var class="product">Model 204</var> FLOD exit feature allows for modification of the record image on which the FLOD (or FILELOAD) command acts. With the FLOD exit feature you can create a COBOL or Assembler program to modify the image records. The FLOD exit feature enables the use of multiple input files for FLOD processing. The exit is modeled on SORT exits, similar to the E15 sort exit. See [[FLOD exits]] for details.</p>

	====Update units====		====Update units====

ELowell at 22:38, 11 December 2013

2013-12-11T22:38:18Z

← Older revision		Revision as of 22:38, 11 December 2013
Line 85:		Line 85:

	====Update units====		====Update units====
	<p>When it processes FLOD, <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see [[~~File_Integrity_and_Recovery~~#Update_units_and_transactions\|Update units and transactions]].</p>		<p>When it processes FLOD, <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. For more information about <var class="product">Model 204</var> update units, see [[File_integrity_and_recovery#Update_units_and_transactions\|Update units and transactions]].</p>
	[[Category: File manager commands]]		[[Category: File manager commands]]
	[[Category:Commands]]		[[Category:Commands]]

ELowell: /* Deferred update data sets */

2013-06-28T18:31:28Z

Deferred update data sets

← Older revision		Revision as of 18:31, 28 June 2013
Line 79:		Line 79:
	</li>		</li>
	</ul>		</ul>
	<p>For more information, see the File management topics on the [[File_Load_Utility:_FLOD_and_FILELOAD_commands\|File Load utility: FLOD and FILELOAD commands]], [[Deferred_Update_Feature\|deferred update ~~data sets~~]], and the [[Z_command\|Z command]].</p>		<p>For more information, see the File management topics on the [[File_Load_Utility:_FLOD_and_FILELOAD_commands\|File Load utility: FLOD and FILELOAD commands]], [[Deferred_Update_Feature\|deferred update feature]], and the [[Z_command\|Z command]].</p>

	====FLOD exit feature====		====FLOD exit feature====

ELowell: /* Deferred update data sets */

2013-06-28T18:29:54Z

Deferred update data sets

← Older revision		Revision as of 18:29, 28 June 2013
Line 79:		Line 79:
	</li>		</li>
	</ul>		</ul>
	<p>For more information, see the File management topics on the [[File_Load_Utility:_FLOD_and_FILELOAD_commands\|File Load utility: FLOD and FILELOAD commands]], [[Deferred_Update_Feature\|deferred update data sets]], and the [[Z_command\|Z command.</p>		<p>For more information, see the File management topics on the [[File_Load_Utility:_FLOD_and_FILELOAD_commands\|File Load utility: FLOD and FILELOAD commands]], [[Deferred_Update_Feature\|deferred update data sets]], and the [[Z_command\|Z command]].</p>

	====FLOD exit feature====		====FLOD exit feature====

ELowell: /* Deferred update data sets */

2013-06-28T18:29:04Z

Deferred update data sets

← Older revision		Revision as of 18:29, 28 June 2013
Line 79:		Line 79:
	</li>		</li>
	</ul>		</ul>
	<p>For more information, see the File management topics on the [[File_Load_Utility:_FLOD_and_FILELOAD_commands\|File Load utility: FLOD and FILELOAD commands]], [[Deferred_Update_Feature\|deferred update data sets]], [[Z_command\|Z command~~]], and input data set requirements~~.</p>		<p>For more information, see the File management topics on the [[File_Load_Utility:_FLOD_and_FILELOAD_commands\|File Load utility: FLOD and FILELOAD commands]], [[Deferred_Update_Feature\|deferred update data sets]], and the [[Z_command\|Z command.</p>

	====FLOD exit feature====		====FLOD exit feature====

ELowell: /* Deferred update data sets */

2013-06-28T18:26:18Z

Deferred update data sets

← Older revision		Revision as of 18:26, 28 June 2013
Line 79:		Line 79:
	</li>		</li>
	</ul>		</ul>
	<p>For more information, see the File management topics on the [[File_Load_Utility:_FLOD_and_FILELOAD_commands\|~~FLOD command and~~ File Load utility]], [[Deferred_Update_Feature\|deferred update data sets]], [[Z_command\|Z command]], and input data set requirements.</p>		<p>For more information, see the File management topics on the [[File_Load_Utility:_FLOD_and_FILELOAD_commands\|File Load utility: FLOD and FILELOAD commands]], [[Deferred_Update_Feature\|deferred update data sets]], [[Z_command\|Z command]], and input data set requirements.</p>

	====FLOD exit feature====		====FLOD exit feature====