FILEORG parameter - Revision history

JAL: /* Description */ add link

2017-07-11T23:07:56Z

Description: add link

← Older revision		Revision as of 23:07, 11 July 2017
Line 23:		Line 23:
	<tr class="head"><th>Setting</th><th>Meaning</th></tr>		<tr class="head"><th>Setting</th><th>Meaning</th></tr>
	<tr><th align="right"><var>X'200'</var></th>		<tr><th align="right"><var>X'200'</var></th>
	<td>Large file support.		<td>[[File design#x200\|Large file support.]] </td></tr>
	~~<p>Allows files to hold up to 48M (50,331,648) records. (Without this setting, the limit is 16M records.)</p>~~
	~~<p>May not be used in sorted (<var>FILEORG</var> X'01') nor hashed (<var>FILEORG</var> X'08') files.</p>~~
	~~<p>For information on this setting and deferred updates, see [[Deferred update feature#Deferred updates and large .28FILEORG_X.27200.27.29 files\|Deferred updates~~]]~~.</p>~~
	~~<p>~~
	~~Available as of Model 204 V7.5.</p>~~</td></tr>

	<tr><th align="right"><var>X'100'</var></th>		<tr><th align="right"><var>X'100'</var></th>

ELowell: /* Description */

2017-03-13T18:52:30Z

Description

← Older revision		Revision as of 18:52, 13 March 2017
Line 18:		Line 18:
	The file ([[Table B (File architecture)\|Table B]]) organization.</p>		The file ([[Table B (File architecture)\|Table B]]) organization.</p>
	<p>		<p>
			<div id="large_files"></div>
	Valid settings of <var>FILEORG</var> are:</p>		Valid settings of <var>FILEORG</var> are:</p>
	~~<div id="large_files"></div>~~
	<table>		<table>
	<tr class="head"><th>Setting</th><th>Meaning</th></tr>		<tr class="head"><th>Setting</th><th>Meaning</th></tr>

ELowell: /* Description */

2017-03-13T18:48:50Z

Description

← Older revision		Revision as of 18:48, 13 March 2017
Line 19:		Line 19:
	<p>		<p>
	Valid settings of <var>FILEORG</var> are:</p>		Valid settings of <var>FILEORG</var> are:</p>
			<div id="large_files"></div>
	<table>		<table>
	<tr class="head"><th>Setting</th><th>Meaning</th></tr>		<tr class="head"><th>Setting</th><th>Meaning</th></tr>

ELowell: /* Description */

2017-03-10T23:03:44Z

Description

← Older revision		Revision as of 23:03, 10 March 2017
Line 23:		Line 23:
	<tr><th align="right"><var>X'200'</var></th>		<tr><th align="right"><var>X'200'</var></th>
	<td>Large file support.		<td>Large file support.
	<p>Allows files to hold up to 48M (50,331,648) records.~~</p>~~		<p>Allows files to hold up to 48M (50,331,648) records. (Without this setting, the limit is 16M records.)</p>
	~~<p>~~Without this setting, the limit is 16M records.</p>		<p>May not be used in sorted (<var>FILEORG</var> X'01') nor hashed (<var>FILEORG</var> X'08') files.</p>
	<p>May not be used in sorted (<var>FILEORG</var> X'01') nor hashed (<var>FILEORG</var> X'08') files.		<p>For information on this setting and deferred updates, see [[Deferred update feature#Deferred updates and large .28FILEORG_X.27200.27.29 files\|Deferred updates]].</p>
	</p>
	<p>		<p>
	Available as of Model 204 V7.5.</p></td></tr>		Available as of Model 204 V7.5.</p></td></tr>

ELowell at 22:26, 10 March 2017

2017-03-10T22:26:25Z

← Older revision		Revision as of 22:26, 10 March 2017
Line 23:		Line 23:
	<tr><th align="right"><var>X'200'</var></th>		<tr><th align="right"><var>X'200'</var></th>
	<td>Large file support.		<td>Large file support.
	<p>Allows files to hold up to ~~48 M~~ (50,331,648) records.</p>		<p>Allows files to hold up to 48M (50,331,648) records.</p>
	<p>Without this setting, the limit is 16M records.</p>		<p>Without this setting, the limit is 16M records.</p>
	<p>May not be used in sorted (<var>FILEORG</var> X'01') nor hashed (<var>FILEORG</var> X'08') files.		<p>May not be used in sorted (<var>FILEORG</var> X'01') nor hashed (<var>FILEORG</var> X'08') files.

ELowell: /* Description */

2017-03-10T22:25:29Z

Description

← Older revision		Revision as of 22:25, 10 March 2017
Line 23:		Line 23:
	<tr><th align="right"><var>X'200'</var></th>		<tr><th align="right"><var>X'200'</var></th>
	<td>Large file support.		<td>Large file support.
	<p>		<p>Allows files to hold up to 48 M (50,331,648) records.</p>
	Allows files to hold up to 48 M (50,331,648) records.</p>		<p>Without this setting, the limit is 16M records.</p>
	<p>May not be used in sorted (<var>FILEORG</var> X'01') nor hashed (<var>FILEORG</var> X'08') files.		<p>May not be used in sorted (<var>FILEORG</var> X'01') nor hashed (<var>FILEORG</var> X'08') files.
	</p>		</p>

ELowell at 19:27, 9 August 2016

2016-08-09T19:27:32Z

← Older revision		Revision as of 19:27, 9 August 2016
Line 28:		Line 28:
	</p>		</p>
	<p>		<p>
	Available ~~from~~ Model 204 V7.5.</p></td></tr>		Available as of Model 204 V7.5.</p></td></tr>

	<tr><th align="right"><var>X'100'</var></th>		<tr><th align="right"><var>X'100'</var></th>
Line 43:		Line 43:
	If the <var>FILEORG</var> X'100' bit is set, the X'80' option is automatically set.</p>		If the <var>FILEORG</var> X'100' bit is set, the X'80' option is automatically set.</p>
	<p>		<p>
	Available in Model 204 V7.5.</p></td></tr>		Available as of Model 204 V7.5.</p></td></tr>

	<tr><th align="right"><var>X'80'</var></th>		<tr><th align="right"><var>X'80'</var></th>

JAL: link repair

2016-02-19T16:56:02Z

link repair

← Older revision		Revision as of 16:56, 19 February 2016
Line 39:		Line 39:
	Some or all of this additional overhead space can be won back when certain <var>FILEORG</var> X'100' features come into play, such as <var>FLOAT/BINARY</var> field value compression and the use of fieldgroups to eliminate placeholder fields. However, if a file is converted to a <var>FILEORG</var> X'100' file without taking advantage of fieldgroups, and the file contains no compressible <var>FLOAT/BINARY</var> fields (because there are no such fields, or their values are large and thus uncompressible), then an increase in Table B space requirements is likely.</p>		Some or all of this additional overhead space can be won back when certain <var>FILEORG</var> X'100' features come into play, such as <var>FLOAT/BINARY</var> field value compression and the use of fieldgroups to eliminate placeholder fields. However, if a file is converted to a <var>FILEORG</var> X'100' file without taking advantage of fieldgroups, and the file contains no compressible <var>FLOAT/BINARY</var> fields (because there are no such fields, or their values are large and thus uncompressible), then an increase in Table B space requirements is likely.</p>
	<p>		<p>
	<var>FILEORG</var> X'100' files cannot be loaded via <var>[[FLOD_command\|FLOD]]</var> or <var>[[FILELOAD_command\|FILELOAD]]</var> except with a <var class="product">[[~~Media:FrelrNew.pdf\|~~Fast/Reload]]</~~var> <~~var>Load All Information~~</var>~~ (<var>LAI</var>) <var>FLOD/FILELOAD</var> program.</p>		<var>FILEORG</var> X'100' files cannot be loaded via <var>[[FLOD_command\|FLOD]]</var> or <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>) <var>FLOD/FILELOAD</var> program.</p>
	<p>		<p>
	If the <var>FILEORG</var> X'100' bit is set, the X'80' option is automatically set.</p>		If the <var>FILEORG</var> X'100' bit is set, the X'80' option is automatically set.</p>

JAL: typo

2016-02-17T01:31:38Z

typo

← Older revision		Revision as of 01:31, 17 February 2016
Line 63:		Line 63:
	<td>[[Hash key files\|Hash key file]].</td></tr>		<td>[[Hash key files\|Hash key file]].</td></tr>

	<tr><th align="right"><var> X'04'</var></th><td~~><var~~>[[~~File_design~~#~~Reuse_Record_Number_~~.28X.~~2740~~.27.29\|Reuse record number (RRN)]]~~</var>~~.		<tr><th align="right"><var> X'04'</var></th><td>[[File design#Reuse Record Number .28X.2704.27.29\|Reuse record number (RRN)]].
	<p>This option can be added to any other <var>FILEORG</var> option. If this option is set without the hash key (X'08') or sorted (X'01') options, the unordered option (X'20') is automatically set.</p></td></tr>		<p>This option can be added to any other <var>FILEORG</var> option. If this option is set without the hash key (X'08') or sorted (X'01') options, the unordered option (X'20') is automatically set.</p></td></tr>

JAL: /* Description */ trivial tweak

2015-04-10T19:07:08Z

Description: trivial tweak

← Older revision		Revision as of 19:07, 10 April 2015
Line 33:		Line 33:
	<td>Enhanced data handling files.		<td>Enhanced data handling files.
	<p>		<p>
	Enables a number of enhancements to the file structure, including support for [[Field group (File architecture)\| physical field groups]]; the definition of up to 32000 fields in a file; system maintained [[Field design#Automatic fields\|automatic fields]]; [[Field design#Field constraints\|field constraints]] providing content validation; and improved space management of fields containing [[Field design#BLOB~~.2C_CLOB.2C_and_MINLOBE_attributes~~\|large objects]]. </p>		Enables a number of enhancements to the file structure, including support for [[Field group (File architecture)\|physical field groups]]; the definition of up to 32000 fields in a file; system maintained [[Field design#Automatic fields\|automatic fields]]; [[Field design#Field constraints\|field constraints]] providing content validation; and improved space management of fields containing [[Field design#BLOB, CLOB, and MINLOBE attributes\|large objects]]. </p>
	<p>		<p>
	<var>FILEORG</var> X'100' files have a fixed overhead of 4 bytes in Table B for each field occurrence as opposed to 3 bytes for <var>FILEORG</var> X'80' files, 3 bytes for [[~~Field_design~~#~~STRING_attribute~~\|string]] fields, and 2 bytes for other fields in other files. In addition, <var>FILEORG</var> X'100' files have a 4-byte overhead per record for a field group ID counter. This overhead is in addition to the space required for the actual values. </p>		<var>FILEORG</var> X'100' files have a fixed overhead of 4 bytes in Table B for each field occurrence as opposed to 3 bytes for <var>FILEORG</var> X'80' files, 3 bytes for [[Field design#STRING attribute\|string]] fields, and 2 bytes for other fields in other files. In addition, <var>FILEORG</var> X'100' files have a 4-byte overhead per record for a field group ID counter. This overhead is in addition to the space required for the actual values. </p>
	<p>		<p>
	Some or all of this additional overhead space can be won back when certain <var>FILEORG</var> X'100' features come into play, such as <var>FLOAT/BINARY</var> field value compression and the use of fieldgroups to eliminate placeholder fields. However, if a file is converted to a <var>FILEORG</var> X'100' file without taking advantage of fieldgroups, and the file contains no compressible <var>FLOAT/BINARY</var> fields (because there are no such fields, or their values are large and thus uncompressible), then an increase in Table B space requirements is likely.</p>		Some or all of this additional overhead space can be won back when certain <var>FILEORG</var> X'100' features come into play, such as <var>FLOAT/BINARY</var> field value compression and the use of fieldgroups to eliminate placeholder fields. However, if a file is converted to a <var>FILEORG</var> X'100' file without taking advantage of fieldgroups, and the file contains no compressible <var>FLOAT/BINARY</var> fields (because there are no such fields, or their values are large and thus uncompressible), then an increase in Table B space requirements is likely.</p>