Record loops - Revision history

DCameron: /* Noting character strings */

2018-11-29T14:16:51Z

Noting character strings

← Older revision		Revision as of 14:16, 29 November 2018
Line 996:		Line 996:
	<p>		<p>
	results in the output:</p>		results in the output:</p>
	<p class="output">2 ~~RECORDS FOR~~ ABBOTT, FRANKLIN G		<p class="output">2 records for ABBOTT, FRANKLIN G
	</p>		</p>
	<p>		<p>

DCameron: /* Noting character strings */

2018-11-29T14:16:18Z

Noting character strings

← Older revision		Revision as of 14:16, 29 November 2018
Line 979:		Line 979:
	<p>		<p>
	The following form of the <var>Note</var> statement can be used to set a value for later reference by the <var>Value In</var> phrase: </p>		The following form of the <var>Note</var> statement can be used to set a value for later reference by the <var>Value In</var> phrase: </p>
	<p class="code">label: ~~NOTE~~ 'string'		<p class="code">label: note 'string'
	</p>		</p>
	<p>		<p>
	For example:</p>		For example:</p>
	<p class="code">~~BEGIN~~		<p class="code">Begin
	~~NAME~~: ~~NOTE~~ 'ABBOTT, FRANKLIN G'		name: note 'ABBOTT, FRANKLIN G'
	~~FIND~~.~~RECS~~: ~~FIND ALL RECORDS FOR WHICH~~		find.recs: find all records for which
	~~FULLNAME~~ = ~~VALUE IN NAME~~		fullname = value in name
	~~END FIND~~		end find
	CT: ~~COUNT RECORDS IN FIND~~.~~RECS~~		ct: count records in find.recs
	~~PRINT COUNT IN CT~~ -		print count in ct -
	~~WITH~~ ' ~~RECORDS FOR~~ ' -		with ' records for ' -
	~~WITH VALUE IN NAME~~		with value in name
	~~END~~		end
	</p>		</p>
	<p>		<p>

JAL: /* Print All Information (or PAI) Into statement */ mixed case for UL

2018-06-08T00:53:37Z

Print All Information (or PAI) Into statement: mixed case for UL

← Older revision		Revision as of 00:53, 8 June 2018
Line 1,189:		Line 1,189:
	<li><var class="term">option</var> can be one of the following, specifying how Large Object fields are handled:		<li><var class="term">option</var> can be one of the following, specifying how Large Object fields are handled:
	<ul>		<ul>
	<li>~~LOB_DATA —~~ If the LOB is 255 bytes or less and the field value array element is large enough, the LOB data is copied to the field value array element. Otherwise, <var>$Status</var> is set to 2, <var>$StatusD</var> is set to 3, and the entire record is output in <var>PAI</var> format to the output device.		<li><var>Lob_Data</var>
			<p>If the LOB is 255 bytes or less and the field value array element is large enough, the LOB data is copied to the field value array element. Otherwise, <var>$Status</var> is set to 2, <var>$StatusD</var> is set to 3, and the entire record is output in <var>PAI</var> format to the output device. </p>
	<p>		<p>
	~~The~~ default option for the <var>PAI Into</var> statement ~~is LOB_DATA~~. </p></li>		<var>Lob_Data</var> is the default option for the <var>PAI Into</var> statement. </p></li>

	<li>~~LOB_SHORT_DATA —~~ Copies the first 255 bytes of the LOB data to the field value array element. </li>		<li><var>Lob_Short_Data</var>
			<p>
			Copies the first 255 bytes of the LOB data to the field value array element. </p></li>

	<li>~~LOB_NO_DATA —~~ No LOB data is copied to the field value array. The field name and LOB descriptor are copied to <var class="term">array_1</var> and <var class="term">array_3</var>, respectively. </li>		<li><var>Lob_No_Data</var>
			<p>
			No LOB data is copied to the field value array. The field name and LOB descriptor are copied to <var class="term">array_1</var> and <var class="term">array_3</var>, respectively. </p></li>

	<li>~~LOB_NONE —~~ No LOB information (field name, LOB data, nor LOB descriptor) is copied to the output arrays. </li>		<li><var>Lob_None</var>
			<p>
			No LOB information (field name, LOB data, nor LOB descriptor) is copied to the output arrays. </p></li>
	</ul></li>		</ul></li>

JAL: /* PRINT ALL INFORMATION (or PAI) INTO statement */mixed case for stmts

2018-06-08T00:18:36Z

PRINT ALL INFORMATION (or PAI) INTO statement: mixed case for stmts

Show changes

JAL: add ID for PAI Into Example section

2018-06-07T23:43:09Z

add ID for PAI Into Example section

← Older revision		Revision as of 23:43, 7 June 2018
Line 1,269:		Line 1,269:
	When you are using the Parallel Query Option/204 and you are working with a remote file, no locks are issued against the records in the remote file since <var class="product">Model 204</var> works from a local copy of the remote records.</p>		When you are using the Parallel Query Option/204 and you are working with a remote file, no locks are issued against the records in the remote file since <var class="product">Model 204</var> works from a local copy of the remote records.</p>

	===Example===		===<b id="paiIntoExample"></b>Example===
	<p>		<p>
	The following schematic example shows one way to set up a PAI INTO statement to perform a "copy record" function.</p>		The following schematic example shows one way to set up a PAI INTO statement to perform a "copy record" function.</p>

JAL: /* PAI INTO statement */ add link

2018-06-07T23:27:28Z

PAI INTO statement: add link

← Older revision		Revision as of 23:27, 7 June 2018
Line 39:		Line 39:
	The REMEMBER and POSITION statements allow you to store the current processing position in a FOR loop, then recall it at a later time and resume FOR processing where you left off. This technique was developed primarily for use with global found sets and lists, but can be used with non-global found sets and lists as well. See [[Global features#Saving and recalling a POSITION in a FOR loop\|Saving and recalling a POSITION in a FOR loop]] for a detailed discussion of this topic.</p>		The REMEMBER and POSITION statements allow you to store the current processing position in a FOR loop, then recall it at a later time and resume FOR processing where you left off. This technique was developed primarily for use with global found sets and lists, but can be used with non-global found sets and lists as well. See [[Global features#Saving and recalling a POSITION in a FOR loop\|Saving and recalling a POSITION in a FOR loop]] for a detailed discussion of this topic.</p>

	===PAI ~~INTO~~ statement===		===PAI Into statement===
	<p>		<p>
	The PAI ~~INTO~~ statement provides a convenient method to determine field names and values encountered within a <var>For Each Record</var> loop.</p>		The <var>[[#paiInto\|PAI Into]]</var> statement provides a convenient method to determine field names and values encountered within a <var>For Each Record</var> loop. </p>

	==For Each Record statement==		==For Each Record statement==

JAL: /* PRINT ALL INFORMATION (or PAI) INTO statement */ add ID

2018-06-07T23:24:52Z

PRINT ALL INFORMATION (or PAI) INTO statement: add ID

← Older revision		Revision as of 23:24, 7 June 2018
Line 1,175:		Line 1,175:
	However, this technique would be accurate only if the record found by the FIND.RECS statement was not found in any earlier iteration. If the records were found earlier, then a list should be used to arrive at the correct total. [[Lists#Lists\|Lists]] describes the statements used to create lists. </p>		However, this technique would be accurate only if the record found by the FIND.RECS statement was not found in any earlier iteration. If the records were found earlier, then a list should be used to arrive at the correct total. [[Lists#Lists\|Lists]] describes the statements used to create lists. </p>

	==PRINT ALL INFORMATION (or PAI) INTO statement==		==<b id="paiInto"></b>PRINT ALL INFORMATION (or PAI) INTO statement==
	<p>		<p>
	The PRINT ALL INFORMATION (PAI) INTO statement lets you move a record's field names and values into a form of storage that can be easily manipulated. The benefits of the PAI INTO statement include an effective copy-record capability, and also a convenient way to determine field names and values encountered within a <var>For Each Record</var> loop.</p>		The PRINT ALL INFORMATION (PAI) INTO statement lets you move a record's field names and values into a form of storage that can be easily manipulated. The benefits of the PAI INTO statement include an effective copy-record capability, and also a convenient way to determine field names and values encountered within a <var>For Each Record</var> loop.</p>

JAL: add `s`

2018-05-08T19:03:12Z

add <var>s

← Older revision		Revision as of 19:03, 8 May 2018
Line 1,304:		Line 1,304:
	===Null field values===		===Null field values===
	<p>		<p>
	Notice that the ~~ADD~~ statement logic in the previous example includes an ~~ELSE~~ clause that forces processing of null field values. This logic is necessary because assigning a null value from a %variable stores nothing in the output file. If you do not need to copy null field values, then omit this special processing. </p>		Notice that the <var>Add</var> statement logic in the previous example includes an <var>Else</var> clause that forces processing of null field values. This logic is necessary because assigning a null value from a %variable stores nothing in the output file. If you do not need to copy null field values, then omit this special processing. </p>

	</div> <!-- end of toc limit div -->		</div> <!-- end of toc limit div -->

	[[Category:SOUL]]		[[Category:SOUL]]

JAL: /* For Each Record statement */ point to retrieval-conditions syntax on "Statement syntax" page

2018-05-08T18:08:52Z

For Each Record statement: point to retrieval-conditions syntax on "Statement syntax" page

@@ Line 67: / Line 67: @@
 <li><var class="term">%variable</var> or <var class="term">literal</var> specify a numerical increment, which must be greater than or equal to 1. This increment minus 1 is the number of records skipped at each loop iteration.</li>
-<li><var class="term">retrieval-conditions</var> can be:
+<li><var class="term">retrieval-conditions</var> is a simple or arbitrarily complex combination of filtering phrases. For full details, see [[Statement syntax#Retrieval condition syntax|Retrieval condition syntax]]. </li>
 </ul>

JAL: /* Processing records in order */ mixed case for stmts

2018-05-07T20:50:27Z

Processing records in order: mixed case for stmts

← Older revision		Revision as of 20:50, 7 May 2018
Line 323:		Line 323:
	You can use index order processing with fields that were defined with the <var>ORDERED</var> attribute. Record loops in index order execute more slowly than record loops in sort order. </p>		You can use index order processing with fields that were defined with the <var>ORDERED</var> attribute. Record loops in index order execute more slowly than record loops in sort order. </p>
	<p>		<p>
	You can use sort order processing for records in a file ~~which~~ were defined as a sorted file. The execution of a record loop in sort order might be slower than that of an unordered record loop (if you have many spilled records) but faster than that of an index order loop. </p>		You can use sort order processing for records in a file that were defined as a sorted file. The execution of a record loop in sort order might be slower than that of an unordered record loop (if you have many spilled records) but faster than that of an index order loop.
			</p>
	<p class="note"><b>Note:</b> If the <var>In Order</var> option processes a field that is a sort key but also has the <var>ORDERED</var> attribute, and if <var>Sortkey</var> is not specified, index order processing is performed. </p>		<p class="note"><b>Note:</b> If the <var>In Order</var> option processes a field that is a sort key but also has the <var>ORDERED</var> attribute, and if <var>Sortkey</var> is not specified, index order processing is performed. </p>
	<p>		<p>
	If you want to produce a sort order ~~which~~ is not provided for by the syntax of the <var>In Order</var> option, see [[Sorting#Sorting\|Sorting]] for information about the <var>Sort</var> statement.</p>		If you want to produce a sort order that is not provided for by the syntax of the <var>In Order</var> option, see [[Sorting#Sorting\|Sorting]] for information about the <var>Sort</var> statement.</p>

	===Reference context===		===Reference context===
	<p>		<p>
	Index order and sort order processing can be performed only on records from a single file. Therefore, do not use the ~~IN ORDER~~ option with groups in <var>For Each Record</var> loops. Such use of the ~~IN ORDER~~ option with groups results in a counting error and this error message:</p>		Index order and sort order processing can be performed only on records from a single file. Therefore, do not use the <var>In Order</var> option with groups in <var>For Each Record</var> loops. Such use of the <var>In Order</var> option with groups results in a counting error and this error message:</p>
	<p class="code">M204.0243 'IN ORDER' NOT VALID IN GROUP CONTEXT		<p class="code">M204.0243 'IN ORDER' NOT VALID IN GROUP CONTEXT
	</p>		</p>
	<p>		<p>
	If you want to process records from a group in sorted order, use the ~~SORT~~ statement. (~~SORT~~ statement processing typically is slower than index order or sort order processing.)</p>		If you want to process records from a group in sorted order, use the <var>Sort</var> statement. (<var>Sort</var> statement processing typically is slower than index order or sort order processing.) </p>
	<p>		<p>
	The ~~IN ORDER~~ and ~~VALUE IN~~ options are supported in remote file context. See [[#Referring to the current value\|Referring to the current value]] for a discussion of the ~~VALUE IN~~ option.</p>		The <var>In Order</var> and <var>value In</var> options are supported in remote file context. See [[#Referring to the current value\|Referring to the current value]] for a discussion of the <var>Value In</var> option. </p>

	===Specifying processing order===		===Specifying processing order===
	<p>		<p>
	If the fields processed by the <var>For Each Record</var> statement have the ORDERED attribute, or if the file is a sorted file, ordered processing can occur without requiring a separate sort of the found records.</p>		If the fields processed by the <var>For Each Record</var> statement have the <var>ORDERED</var> attribute, or if the file is a sorted file, ordered processing can occur without requiring a separate sort of the found records.</p>
	<p>		<p>
	If the file processed is a sorted file, the ~~SORTKEY~~ option forces records to be processed in order according to the values of the sort key field.</p>		If the file processed is a sorted file, the <var>Sortkey</var> option forces records to be processed in order according to the values of the sort key field. </p>
	<b>Syntax</b>		<b>Syntax</b>
	<p>		<p>

Record loops - Revision history

DCameron: /* Noting character strings */

DCameron: /* Noting character strings */

JAL: /* Print All Information (or PAI) Into statement */ mixed case for UL

JAL: /* PRINT ALL INFORMATION (or PAI) INTO statement */mixed case for stmts

JAL: add ID for PAI Into Example section

JAL: /* PAI INTO statement */ add link

JAL: /* PRINT ALL INFORMATION (or PAI) INTO statement */ add ID

JAL: add s

JAL: /* For Each Record statement */ point to retrieval-conditions syntax on "Statement syntax" page

JAL: /* Processing records in order */ mixed case for stmts

JAL: add `s`