File Load utility: FLOD and FILELOAD commands - Revision history

Alex: /* Example */

2022-06-11T21:33:53Z

Example

← Older revision		Revision as of 21:33, 11 June 2022
Line 664:		Line 664:
	</p>		</p>
	<p>		<p>
	When the <var>CASE</var> statement is executed, the four-character string that starts at position 37 of the input record is compared to each table entry. A match on content and length results in a branch to the procedure label following the <code>=<code>. Thus, if an input record contained <code>JUNE</code> in positions 37-40, control is transferred to procedure label 6. If the record contained <code>JULY</code> or <code>MAY</code>, control is passed to label 7 or 2, respectively.</p>		When the <var>CASE</var> statement is executed, the four-character string that starts at position 37 of the input record is compared to each table entry. A match on content and length results in a branch to the procedure label following the <code>=</code>. Thus, if an input record contained <code>JUNE</code> in positions 37-40, control is transferred to procedure label 6. If the record contained <code>JULY</code> or <code>MAY</code>, control is passed to label 7 or 2, respectively.</p>
	<p>		<p>
	The table entry for <code>MAY</code> in the previous example was expanded to four bytes. If the table entry is as follows, a match does not occur because its implies string length is 3:</p>		The table entry for <code>MAY</code> in the previous example was expanded to four bytes. If the table entry is as follows, a match does not occur because its implies string length is 3:</p>

JAL: link repair

2017-10-20T22:47:04Z

link repair

← Older revision		Revision as of 22:47, 20 October 2017
Line 135:		Line 135:
	<li><var class="term">vl</var> specifies the maximum sort record length in variable-length record sorts. (<var class="term">vl</var> corresponds to the <var>L2</var> of the <var>RECORD</var> sort statement.)		<li><var class="term">vl</var> specifies the maximum sort record length in variable-length record sorts. (<var class="term">vl</var> corresponds to the <var>L2</var> of the <var>RECORD</var> sort statement.)
	<p>		<p>
	The <var class="term">vl</var> parameter is required when <var>ORDERED</var> fields are updated by the file load program. For efficiency, do not use the <var class="term">vl</var> parameter if <var>ORDERED</var> fields are not updated. For more information about the <var class="term">vl</var> parameter and how to select a value for it, see [[Deferred update feature#Setting the variable-length parameter(vl)\|Setting the variable-length parameter(vl)]]. </p></li>		The <var class="term">vl</var> parameter is required when <var>ORDERED</var> fields are updated by the file load program. For efficiency, do not use the <var class="term">vl</var> parameter if <var>ORDERED</var> fields are not updated. For more information about the <var class="term">vl</var> parameter and how to select a value for it, see [[Deferred update feature#Setting the variable-length sort parameter (vl)\|Setting the variable-length sort parameter (vl)]]. </p></li>
	</ul>		</ul>

JAL: /* Getting information about a FLOD or FILELOAD run */ link repair

2017-10-20T20:00:24Z

Getting information about a FLOD or FILELOAD run: link repair

← Older revision		Revision as of 20:00, 20 October 2017
Line 28:		Line 28:
	===Getting information about a FLOD or FILELOAD run===		===Getting information about a FLOD or FILELOAD run===
	<p>		<p>
	Some of the characteristics of the File Load run such as the number of records deleted or the number of fields added during the run are kept as counters that are printed at the end of the run. These counters are listed in [[#FLOD and FILELOAD command output\|FLOD and FILELOAD command output]]. A histogram listing the distribution of deferred update record lengths along with the number of records for each range of lengths is also displayed for variable-length deferred update data sets. It can be used as an aid to setting the variable-length sort parameter, and is illustrated in [[Deferred update feature#Setting the variable-length parameter(vl)\|Setting the variable-length parameter(vl)]]. </p>		Some of the characteristics of the File Load run such as the number of records deleted or the number of fields added during the run are kept as counters that are printed at the end of the run. These counters are listed in [[#FLOD and FILELOAD command output\|FLOD and FILELOAD command output]]. A histogram listing the distribution of deferred update record lengths along with the number of records for each range of lengths is also displayed for variable-length deferred update data sets. It can be used as an aid to setting the variable-length sort parameter, and is illustrated in [[Deferred update feature#Setting the variable-length sort parameter (vl)\|Setting the variable-length sort parameter (vl)]]. </p>

	==Double-checking your file load run==		==Double-checking your file load run==

JAL: add link to Fast/Reload

2017-05-09T19:22:04Z

add link to Fast/Reload

← Older revision		Revision as of 19:22, 9 May 2017
Line 9:		Line 9:
	<p>		<p>
	These commands place the file in deferred update mode, in which updates to Tables C and D are deferred to deferred update data sets and are applied later to Tables C and D.</p>		These commands place the file in deferred update mode, in which updates to Tables C and D are deferred to deferred update data sets and are applied later to Tables C and D.</p>
	<p class="note"><b>~~Note~~:</b>		<blockquote class="note">
	<var>FILEORG</var> X'100' files cannot be loaded ~~via~~ <var>~~[[FLOD_command\|~~FLOD]]</var> or		<b>Notes:</b>
	<var>~~[[FILELOAD_command\|~~FILELOAD]]</var> except with a <var class="product">[[Fast/Reload]]</var> Load All Information (<var>[[Fast/Reload statements#The LAI statement\|LAI]]</var>)		<ul>
	<var>FLOD/FILELOAD</var> program.</p>		<li>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. </li>

			<li><var>[[FILEORG parameter\|FILEORG]]</var> X'100' files cannot be loaded by <var>FLOD</var> or
			<var>FILELOAD</var> except with a <var class="product">Fast/Reload</var> Load All Information (<var>[[Fast/Reload statements#The LAI statement\|LAI]]</var>) <var>FLOD/FILELOAD</var> program.</li>
			</ul>
			</blockquote>
			<br>

	===Including the FLOD or FILELOAD command in your run===		===Including the FLOD or FILELOAD command in your run===
Line 412:		Line 418:
	==File Load statements: loading a new Model 204 file==		==File Load statements: loading a new Model 204 file==
	<p>		<p>
	The statements that can be used in a file load program are summarized here. Most file load statements are sensitive to the column in which they begin; note the specifications carefully. </p>		The statements that can be used in a file load program are summarized here, with the exceptions of the <var>[[Fast/Reload statements#The OPTIONS statement\|OPTIONS]]</var> and <var>[[Fast/Reload statements#The LAI statement\|LAI]]</var> statements, which are valid only if [[Fast/Reload]] is authorized at your site. In addition, those of the statements summarized here that are not valid for Fast/Reload are so noted.</p>
			<p>
			Most file load statements are sensitive to the column in which they begin; note the specifications carefully. </p>
	<p class="note"><b>Note:</b>		<p class="note"><b>Note:</b>
	The file load statements use the vertical bar (<tt>\|</tt>) character (that is, the character that has the hexadecimal value X'4F'). If the vertical bar is not available on the terminal being used for the File Load run, use the up-arrow (<tt>↑</tt>) or caret (<tt>^</tt>) instead. The broken vertical bar symbol available on some ASCII terminals is not equivalent to the vertical bar. Use the up-arrow or caret for these terminals.</p>		The file load statements use the vertical bar (<tt>\|</tt>) character (that is, the character that has the hexadecimal value X'4F'). If the vertical bar is not available on the terminal being used for the File Load run, use the up-arrow (<tt>↑</tt>) or caret (<tt>^</tt>) instead. The broken vertical bar symbol available on some ASCII terminals is not equivalent to the vertical bar. Use the up-arrow or caret for these terminals.</p>
Line 1,392:		Line 1,400:

	===L...ENDL statement (locate existing records)===		===L...ENDL statement (locate existing records)===
			<p class="note"><b>Note:</b> The <var>L</var> and <var>ENDL</var> statements are not supported by [[Fast/Reload statements#Overview\|Fast/Reload]]. </p>
	<p>		<p>
	The <var>L</var> statement provides a means of locating all the existing records in the <var class="product">Model 204</var> file with a specified field name = value pair. The field must be a <var>KEY</var> or <var>ORDERED</var> field. One pass is then made through a locate loop of file load statements for each record located in this way.</p>		The <var>L</var> statement provides a means of locating all the existing records in the <var class="product">Model 204</var> file with a specified field name = value pair. The field must be a <var>KEY</var> or <var>ORDERED</var> field. One pass is then made through a locate loop of file load statements for each record located in this way.</p>
	~~<p>~~
	Beginning in <var class="product">Model 204</var> V4R2.0, the <var>L</var> statement supports the <var>ORDERED</var> attribute as well as the <var>KEY</var> attribute. Prior to V4R2.0, you might have defined fields in your files with both the <var>KEY</var> and <var>ORDERED</var> attributes, because you needed the <var>KEY</var> attribute for File Load <var>L</var> statement usage. In such cases, removing the <var>KEY</var> attribute eliminates Table C usage for that field and saves CPU time and disk I/O. </p>
	<p>		<p>
	During a particular pass, the located record becomes the current record (that is, the record updated by [[#rdLoadStmt\|read-and-load-a-field]] statements, <var>[[#delStmt\|DELETE]]</var> statements, and so on). Whatever <var class="product">Model 204</var> record was current before the L statement is remembered and becomes the current record again when all the located records have been processed by the locate loop.</p>		During a particular pass, the located record becomes the current record (that is, the record updated by [[#rdLoadStmt\|read-and-load-a-field]] statements, <var>[[#delStmt\|DELETE]]</var> statements, and so on). Whatever <var class="product">Model 204</var> record was current before the L statement is remembered and becomes the current record again when all the located records have been processed by the locate loop.</p>
Line 1,467:		Line 1,474:

	===<b id="upStmt"></b>UP and DOWN statements (change record processing level)===		===<b id="upStmt"></b>UP and DOWN statements (change record processing level)===
			<p class="note"><b>Note:</b> The <var>UP</var> and <var>DOWN</var> statements are not supported by [[Fast/Reload statements#Overview\|Fast/Reload]]. </p>
	<p>		<p>
	The current record processing position can be changed through use of the <var>UP</var> and <var>DOWN</var> statements. The <var>UP</var> and <var>DOWN</var> statements consist of words starting in column 1. They can be used only within locate loops: </p>		The current record processing position can be changed through use of the <var>UP</var> and <var>DOWN</var> statements. The <var>UP</var> and <var>DOWN</var> statements consist of words starting in column 1. They can be used only within locate loops: </p>
Line 1,502:		Line 1,510:

	===F statement (read field values)===		===F statement (read field values)===
			<p class="note"><b>Note:</b> The <var>F</var> and <var>ENDF</var> statements are not supported by [[Fast/Reload statements#Overview\|Fast/Reload]]. </p>
	<p>		<p>
	The <var>F</var> statement provides a means of reading the current value(s) of a specified field within the current record. One pass is made through an <var>F</var> loop of file load statements for each occurrence of the field within the record. </p>		The <var>F</var> statement provides a means of reading the current value(s) of a specified field within the current record. One pass is made through an <var>F</var> loop of file load statements for each occurrence of the field within the record. </p>
Line 1,548:		Line 1,557:

	===<b id="delStmt"></b>Deleting a record===		===<b id="delStmt"></b>Deleting a record===
			<p class="note"><b>Note:</b> The <var>DELETE</var> statement is not supported by [[Fast/Reload statements#Overview\|Fast/Reload]]. </p>
	<p>		<p>
	The <var>DELETE</var> statement deletes the current <var class="product">Model 204</var> record from the file. This statement consists of the word <var>DELETE</var> in column 1. </p>		The <var>DELETE</var> statement deletes the current <var class="product">Model 204</var> record from the file. This statement consists of the word <var>DELETE</var> in column 1. </p>
Line 1,694:		Line 1,704:
	This section describes the file load program error conditions that <var class="product">Model 204</var> can encounter because of preallocated field and field-level security violations. </p>		This section describes the file load program error conditions that <var class="product">Model 204</var> can encounter because of preallocated field and field-level security violations. </p>
	<p>		<p>
	Errors generated during file load program evaluation are <b>counting errors</b>, which are described in ~~the <var class="book">~~[[~~Media:M204_TerminalUserGuide_V75.pdf~~\|~~Rocket Model 204 Terminal User's Guide~~]]~~</var>~~. If the number of errors encountered during evaluation reaches the limit specified in the <var>ERMX</var> parameter, the file load program is terminated and the user is restarted. </p>		Errors generated during file load program evaluation are <b>counting errors</b>, which are described in [[Terminal session#Counting errors\|Counting errors]]. If the number of errors encountered during evaluation reaches the limit specified in the <var>ERMX</var> parameter, the file load program is terminated and the user is restarted. </p>

	====File load performance====		====File load performance====

Dme: /* UP and DOWN statements (change record processing level) */

2016-10-27T17:30:10Z

UP and DOWN statements (change record processing level)

← Older revision		Revision as of 17:30, 27 October 2016
Line 1,466:		Line 1,466:
	</p>		</p>

	===UP and DOWN statements (change record processing level)===		===<b id="upStmt"></b>UP and DOWN statements (change record processing level)===
	<p>		<p>
	The current record processing position can be changed through use of the <var>UP</var> and <var>DOWN</var> statements. The <var>UP</var> and <var>DOWN</var> statements consist of words starting in column 1. They can be used only within locate loops: </p>		The current record processing position can be changed through use of the <var>UP</var> and <var>DOWN</var> statements. The <var>UP</var> and <var>DOWN</var> statements consist of words starting in column 1. They can be used only within locate loops: </p>

Dme: /* Deleting a record */

2016-10-27T17:28:50Z

Deleting a record

← Older revision		Revision as of 17:28, 27 October 2016
Line 1,547:		Line 1,547:
	==File Load statements: deleting records and fields==		==File Load statements: deleting records and fields==

	===Deleting a record===		===<b id="delStmt"></b>Deleting a record===
	<p>		<p>
	The <var>DELETE</var> statement deletes the current <var class="product">Model 204</var> record from the file. This statement consists of the word <var>DELETE</var> in column 1. </p>		The <var>DELETE</var> statement deletes the current <var class="product">Model 204</var> record from the file. This statement consists of the word <var>DELETE</var> in column 1. </p>

Dme: /* Read-and-load-a-field statement */

2016-10-27T17:27:37Z

Read-and-load-a-field statement

← Older revision		Revision as of 17:27, 27 October 2016
Line 435:		Line 435:
	</p>		</p>

	===<b id="rdLoadStmt></b>Read-and-load-a-field statement===		===<b id="rdLoadStmt"></b>Read-and-load-a-field statement===
	<p>		<p>
	The read-and-load-a-field statement stores a field (in a <var class="product">Model 204</var> record) that contains the specified field name and a value extracted from the specified positions of the current input record. </p>		The read-and-load-a-field statement stores a field (in a <var class="product">Model 204</var> record) that contains the specified field name and a value extracted from the specified positions of the current input record. </p>

Dme: /* Read-and-load-a-field statement */

2016-10-27T17:26:35Z

Read-and-load-a-field statement

← Older revision		Revision as of 17:26, 27 October 2016
Line 435:		Line 435:
	</p>		</p>

	===Read-and-load-a-field statement===		===<b id="rdLoadStmt></b>Read-and-load-a-field statement===
	<p>		<p>
	The read-and-load-a-field statement stores a field (in a <var class="product">Model 204</var> record) that contains the specified field name and a value extracted from the specified positions of the current input record. </p>		The read-and-load-a-field statement stores a field (in a <var class="product">Model 204</var> record) that contains the specified field name and a value extracted from the specified positions of the current input record. </p>

Dme: /* L...ENDL statement (locate existing records) */

2016-10-27T17:25:48Z

L...ENDL statement (locate existing records)

← Older revision		Revision as of 17:25, 27 October 2016
Line 1,397:		Line 1,397:
	Beginning in <var class="product">Model 204</var> V4R2.0, the <var>L</var> statement supports the <var>ORDERED</var> attribute as well as the <var>KEY</var> attribute. Prior to V4R2.0, you might have defined fields in your files with both the <var>KEY</var> and <var>ORDERED</var> attributes, because you needed the <var>KEY</var> attribute for File Load <var>L</var> statement usage. In such cases, removing the <var>KEY</var> attribute eliminates Table C usage for that field and saves CPU time and disk I/O. </p>		Beginning in <var class="product">Model 204</var> V4R2.0, the <var>L</var> statement supports the <var>ORDERED</var> attribute as well as the <var>KEY</var> attribute. Prior to V4R2.0, you might have defined fields in your files with both the <var>KEY</var> and <var>ORDERED</var> attributes, because you needed the <var>KEY</var> attribute for File Load <var>L</var> statement usage. In such cases, removing the <var>KEY</var> attribute eliminates Table C usage for that field and saves CPU time and disk I/O. </p>
	<p>		<p>
	During a particular pass, the located record becomes the current record (that is, the record updated by read-and-load-a-field statements, ~~delete~~ statements, and so on). ~~If a new~~ <var class="product">Model 204</var> record ~~has begun~~ before the L statement~~, it~~ is remembered and becomes the current record again when all the located records have been processed by the locate loop. If no records contain the specified field name = value pair, no passes are made through the locate loop. </p>		During a particular pass, the located record becomes the current record (that is, the record updated by [[#rdLoadStmt\|read-and-load-a-field]] statements, <var>[[#delStmt\|DELETE]]</var> statements, and so on). Whatever <var class="product">Model 204</var> record was current before the L statement is remembered and becomes the current record again when all the located records have been processed by the locate loop.</p>
			<p>
			Within an <var>L</var> loop, <var>[[#upStmt\|UP]]</var> statements can be used to process records which were current outside the loop.</p>
			<p>
			If no records contain the specified field name = value pair, no passes are made through the locate loop. </p>
	<p>		<p>
	A locate loop that follows an L statement consists of a sequence of file load statements followed by an <var>ENDL</var> statement. You can use any file load statement except one that transfers control to a label outside the loop (that is, a label that is not between the <var>L</var> and <var>ENDL</var> statements). </p>		A locate loop that follows an L statement consists of a sequence of file load statements followed by an <var>ENDL</var> statement. You can use any file load statement except one that transfers control to a label outside the loop (that is, a label that is not between the <var>L</var> and <var>ENDL</var> statements). </p>

Dme: /* Handling the date-time stamp field in a file */

2016-10-27T17:15:46Z

Handling the date-time stamp field in a file

← Older revision		Revision as of 17:15, 27 October 2016
Line 1,631:		Line 1,631:
	<p>		<p>
	The <var>DELETE FIELD</var> command is prohibited for the <var>DTSFN</var> field in a file when the <var>FOPT</var> X'10' bit is set. Attempting to do so results in the following message:</p>		The <var>DELETE FIELD</var> command is prohibited for the <var>DTSFN</var> field in a file when the <var>FOPT</var> X'10' bit is set. Attempting to do so results in the following message:</p>
	<p class="code">M204.2727: ~~CAN~~'~~T DELETE~~ DTS ~~FIELD WHEN~~ FOPT=X'10' ~~IS ON~~		<p class="code">M204.2727: Can't delete DTS field when FOPT=X'10' is on
	</p>		</p>