Sorting - Revision history

Dme at 13:19, 31 December 2018

2018-12-31T13:19:41Z

← Older revision		Revision as of 13:19, 31 December 2018
Line 169:		Line 169:
	<p>		<p>
	This discrepancy does not exist, however, when updating records through a sorted record set that was produced with the SORT RECORD KEYS statement. For the SORT RECORD KEYS statement, only the sort keys and the Table B record number are copied. Inside the FOR EACH RECORD loop, data extraction takes place from the original Table B record. </p>		This discrepancy does not exist, however, when updating records through a sorted record set that was produced with the SORT RECORD KEYS statement. For the SORT RECORD KEYS statement, only the sort keys and the Table B record number are copied. Inside the FOR EACH RECORD loop, data extraction takes place from the original Table B record. </p>


	====Prior to Model 204 V4R2.0: update statements on sorted set not allowed====		====Prior to Model 204 V4R2.0: update statements on sorted set not allowed====

Dme at 13:13, 31 December 2018

2018-12-31T13:13:31Z

← Older revision		Revision as of 13:13, 31 December 2018
Line 158:		Line 158:
	</table>		</table>

	===Copy produced===		===<b id="srtRecsUpd"></b>Copy produced; updating considerations===
	<p>		<p>
	The records in the sorted copy contain only the fields required to complete the original request. Therefore only those fields are available if the sorted copy is referred to by a later request continuation (see [[Large request considerations#Request continuation\|Request continuation]]).</p>		The records in the sorted copy contain only the fields required to complete the original request. Therefore only those fields are available if the sorted copy is referred to by a later request continuation (see [[Large request considerations#Request continuation\|Request continuation]]).</p>

	====~~Prior to Model 204 V4R2.0~~====		====Updates on sorted set modify the original record set only====
	<p>		<p>
	The SORT RECORDS statement produces a sorted copy of the original ~~records~~ in ~~the~~ CCATEMP ~~file~~; file maintenance ~~cannot be~~ performed directly on the sorted copy. ~~Attempts to add, change, or delete values results~~ in ~~errors~~.</p>		User Language requests can update Table B records from within a FOR EACH RECORD loop that references a sorted record set. The SORT RECORDS statement produces a sorted copy of the original record in CCATEMP; file maintenance is not performed directly on the sorted copy. Any update statement found inside a FOR EACH RECORD loop for the sorted record set updates the original record in Table B of the file.</p>
	<p>		<p>
	~~If the total size of all records to be~~ sorted ~~exceeds 30K~~, ~~only~~ the ~~record keys are~~ sorted~~. The remaining~~ data ~~remains~~ in ~~place~~ in CCATEMP, ~~and~~ the ~~key has a pointer to~~ the ~~data~~, so the ~~data appears to be~~ sorted.</p>		Within a FOR EACH RECORD loop for a sorted record set, data extraction takes place from the sorted copy while data update affects the original record in Table B. Copy records in the CCATEMP sorted set are never updated. In addition, once the update takes place against the Table B record, the sorted copy might no longer match the Table B record. </p>
	<p>		<p>
	~~To update the original record~~, a ~~FOR~~ RECORD ~~NUMBER~~ statement ~~could be used within a~~ FOR EACH RECORD loop~~. Refer to [[Record loops#Processing a single record\|Processing a single~~ record~~]] and [[$CURREC#$CURREC\|$CURREC]] for more information~~.</p>		This discrepancy does not exist, however, when updating records through a sorted record set that was produced with the SORT RECORD KEYS statement. For the SORT RECORD KEYS statement, only the sort keys and the Table B record number are copied. Inside the FOR EACH RECORD loop, data extraction takes place from the original Table B record. </p>


	====~~Beginning with~~ Model 204 V4R2.0====		====Prior to Model 204 V4R2.0: update statements on sorted set not allowed====
	<p>		<p>
	~~User Language requests can update Table B records from within a FOR EACH RECORD loop that references a sorted record set.~~ The SORT RECORDS statement produces a sorted copy of the original ~~record~~ in CCATEMP; file maintenance ~~is not~~ performed directly on the sorted copy. ~~Any update statement found inside a FOR EACH RECORD loop for the sorted record set updates the original record~~ in ~~Table B of the file~~.</p>		The SORT RECORDS statement produces a sorted copy of the original records in the CCATEMP file; file maintenance cannot be performed directly on the sorted copy. Attempts to add, change, or delete values results in errors.</p>
	<p>		<p>
	~~Within a FOR EACH RECORD loop for a~~ sorted ~~record set~~, ~~data extraction takes place from~~ the sorted ~~copy while~~ data ~~update affects the original record~~ in ~~Table B. Copy records~~ in ~~the~~ CCATEMP ~~sorted set are never updated. In addition~~, ~~once~~ the ~~update takes place against~~ the ~~Table B record~~, the sorted ~~copy might no longer match the Table B record~~. </p>		If the total size of all records to be sorted exceeds 30K, only the record keys are sorted. The remaining data remains in place in CCATEMP, and the key has a pointer to the data, so the data appears to be sorted.</p>
	<p>		<p>
	~~This discrepancy does not exist~~, ~~however, when updating records through~~ a ~~sorted record set that was produced with the SORT~~ RECORD ~~KEYS~~ statement~~. For the SORT RECORD KEYS statement, only the sort keys and the Table B record number are copied. Inside the~~ FOR EACH RECORD loop~~, data extraction takes place from the original Table B~~ record. </p>		To update the original record, a FOR RECORD NUMBER statement could be used within a FOR EACH RECORD loop. Refer to [[Record loops#Processing a single record\|Processing a single record]] and [[$CURREC#$CURREC\|$CURREC]] for more information.</p>

	===Using FOR EACH RECORD loops===		===Using FOR EACH RECORD loops===

Dme: /* Syntax for the SORT RECORDS statement */

2018-12-29T20:38:11Z

Syntax for the SORT RECORDS statement

← Older revision		Revision as of 20:38, 29 December 2018
Line 31:		Line 31:
	See [[Sorted files]] for more information about sorting files.</p>		See [[Sorted files]] for more information about sorting files.</p>

	==Syntax for the SORT RECORDS statement==		==<b id="sortRecs"></b>Syntax for the SORT RECORDS statement==
	<p>		<p>
	This section describes the syntax of the SORT RECORDS statement, including a discussion of several of the options. See also [[#Usage guidelines for the SORT RECORDS statement\|Usage guidelines for the SORT RECORDS statement]].</p>		This section describes the syntax of the SORT RECORDS statement, including a discussion of several of the options. See also [[#Usage guidelines for the SORT RECORDS statement\|Usage guidelines for the SORT RECORDS statement]].</p>
Line 117:		Line 117:
	<li>Each set of equal records remains in its retrieved order. If additional sort keys are specified, they are used, one after the other, to order otherwise equal records. </li>		<li>Each set of equal records remains in its retrieved order. If additional sort keys are specified, they are used, one after the other, to order otherwise equal records. </li>
	</ol>		</ol>

	==Usage guidelines for the SORT RECORDS statement==		==Usage guidelines for the SORT RECORDS statement==
	<p>		<p>

JAL: /* IN ORDER clause */ mixed case for stmts

2018-05-11T17:48:25Z

IN ORDER clause: mixed case for stmts

← Older revision		Revision as of 17:48, 11 May 2018
Line 1:		Line 1:
	==Overview==		==Overview==

	===~~IN ORDER~~ clause===		===In Order clause===
	<p>		<p>
	Record retrieval normally creates a found set of records in which the records are held in the order in which they are retrieved.</p>		Record retrieval normally creates a found set of records in which the records are held in the order in which they are retrieved.</p>
	<p>		<p>
	To produce output in sorted order, specify the ~~IN ORDER~~ clause with:</p>		To produce output in sorted order, specify the <var>In Order</var> clause with:</p>
	<ul>		<ul>
	<li>~~FOR EACH RECORD~~ statement, refer to [[Record loops#Processing records in order\|Processing records in order]].</li>		<li><var>For Each Record</var> statement (refer to [[Record loops#Processing records in order\|Processing records in order]]) </li>
	</li>
	<li>~~FOR EACH VALUE~~ statement, refer to [[Value loops#Sorting retrieved values\|Sorting retrieved values]]~~, produces output in sorted order.</li>~~		<li><var>For Each value</var> statement (refer to [[Value loops#Sorting retrieved values\|Sorting retrieved values]]) </li>
	</li>
	</ul>		</ul>
	<p>		<p>
	To use the ~~IN ORDER~~ clause with these statements ~~requires that~~ one of the following conditions ~~exists~~:</p>		To use the <var>In Order</var> clause with these statements, one of the following conditions must exist:</p>
	<ul>		<ul>
	<li>Sort key fields are defined with the [[Field design#ORDERED and NON-ORDERED attributes\|ORDERED]] attribute</li>		<li>Sort key fields are defined with the [[Field design#ORDERED and NON-ORDERED attributes\|ORDERED]] attribute. </li>
	~~</li>~~
	<li>The file is defined as a [[Sorted files\|Sorted]] file.~~</li>~~		<li>The file is defined as a [[Sorted files\|Sorted]] file. </li>
	</li>
	</ul>		</ul>

	===SORT RECORDS statement===		===SORT RECORDS statement===
	<p>		<p>

DCameron: /* Limits of the SORT RECORDS statement */

2015-11-04T16:18:28Z

Limits of the SORT RECORDS statement

← Older revision		Revision as of 16:18, 4 November 2015
Line 141:		Line 141:
	<td>764</td>		<td>764</td>
	</tr>		</tr>
			<tr>
			<td>Individual record size (bytes)</td>
			<td>16,777,216</td>
			</tr>

	<tr>		<tr>
	<td>Total record size (bytes)</td>		<td>Total record size (bytes)</td>
Line 154:		Line 159:
	</tr>		</tr>
	</table>		</table>

	===Copy produced===		===Copy produced===
	<p>		<p>

JAL at 20:31, 5 August 2014

2014-08-05T20:31:44Z

← Older revision		Revision as of 20:31, 5 August 2014
Line 279:		Line 279:
	All sort options and considerations are the same as those for the SORT RECORDS statement, except that SORT RECORD KEYS cannot be used for multiply occurring fields. </p>		All sort options and considerations are the same as those for the SORT RECORDS statement, except that SORT RECORD KEYS cannot be used for multiply occurring fields. </p>
	<p>		<p>
	Special forms of the SORT RECORDS statement exist for use with multiply occurring fields. See [[~~Operations on~~ multiply occurring fields]] for details. </p>		Special forms of the SORT RECORDS statement exist for use with multiply occurring fields. See [[Processing multiply occurring fields and field groups]] for details. </p>

	==Examples==		==Examples==

JAL at 20:30, 5 August 2014

2014-08-05T20:30:56Z

← Older revision		Revision as of 20:30, 5 August 2014
Line 229:		Line 229:
	===Use with multiply occurring fields===		===Use with multiply occurring fields===
	<p>		<p>
	Special forms of the SORT RECORDS statement exist for use with multiply occurring fields. See [[~~Operations on~~ multiply occurring fields#Subscripts\|Subscripts]] and [[~~Operations on~~ multiply occurring fields#SORT RECORDS statement\|SORT RECORDS statement]] for details. </p>		Special forms of the SORT RECORDS statement exist for use with multiply occurring fields. See [[Processing multiply occurring fields and field groups#Subscripts\|Subscripts]] and [[Processing multiply occurring fields and field groups#SORT RECORDS statement\|SORT RECORDS statement]] for details. </p>

	==Field group SORT support==		==Field group SORT support==
Line 332:		Line 332:
	END		END
	</p>		</p>

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

ELowell at 16:48, 12 May 2014

2014-05-12T16:48:39Z

← Older revision		Revision as of 16:48, 12 May 2014
Line 15:		Line 15:
	To use the IN ORDER clause with these statements requires that one of the following conditions exists:</p>		To use the IN ORDER clause with these statements requires that one of the following conditions exists:</p>
	<ul>		<ul>
	<li>Sort key fields are defined with the [[Field design ~~(File management)~~#ORDERED and NON-ORDERED attributes\|ORDERED]] attribute</li>		<li>Sort key fields are defined with the [[Field design#ORDERED and NON-ORDERED attributes\|ORDERED]] attribute</li>
	</li>		</li>
	<li>The file is defined as a [[Sorted files\|Sorted]] file.</li>		<li>The file is defined as a [[Sorted files\|Sorted]] file.</li>

JAL at 18:06, 8 January 2014

2014-01-08T18:06:05Z

Show changes

JAL at 18:03, 2 January 2014

2014-01-02T18:03:56Z

← Older revision		Revision as of 18:03, 2 January 2014
Line 122:		Line 122:

	====Copy produced====		====Copy produced====
	<p>The records in the sorted copy contain only the fields required to complete the original request. Therefore only those fields are available if the sorted copy is referred to by a later request continuation (see [[Large ~~Request Considerations~~#Request continuation\|Request continuation]]).</p>		<p>The records in the sorted copy contain only the fields required to complete the original request. Therefore only those fields are available if the sorted copy is referred to by a later request continuation (see [[Large request considerations#Request continuation\|Request continuation]]).</p>
	<b>Prior to Model 204 V4R2.0</b>		<b>Prior to Model 204 V4R2.0</b>
	<p>The SORT RECORDS statement produces a sorted copy of the original records in the CCATEMP file; file maintenance cannot be performed directly on the sorted copy. Attempts to add, change, or delete values results in errors.</p>		<p>The SORT RECORDS statement produces a sorted copy of the original records in the CCATEMP file; file maintenance cannot be performed directly on the sorted copy. Attempts to add, change, or delete values results in errors.</p>