FILEORG parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
Line 17: Line 17:
<table>
<table>
<tr><th>Setting</th><th>Meaning</th></tr>
<tr><th>Setting</th><th>Meaning</th></tr>
<tr><th align="right"><var>X'100'</var></th><td>Available in Model 204 V7.5.
<tr><th align="right"><var>X'100'</var></th>
<td>Enhanced Data Handling Files:
 
Available in Model 204 V7.5.


Enables a number of enhancements to the file structure, including support for [[File Management Repeating Field Groups|Repeating Field Groups]] (RFGs); the definition of up to 32000 fields in a file; system maintained [[File Management Automatic Fields|Automatic fields]]; [[File Management Field Constraints|Field Constraints]] providing content validation; and improved space management of fields containing [[File Management Large Objects|Large Objects]].  
Enables a number of enhancements to the file structure, including support for [[File Management Repeating Field Groups|Repeating Field Groups]] (RFGs); the definition of up to 32000 fields in a file; system maintained [[File Management Automatic Fields|Automatic fields]]; [[File Management Field Constraints|Field Constraints]] providing content validation; and improved space management of fields containing [[File Management Large Objects|Large Objects]].  


If selected, the X'80' bit is automatically set.</td></tr>
If selected, the X'80' bit is automatically set.</td></tr>
<tr><th align="right"><var>X'80'</var></th><td>All nonpreallocated (non-OCCURS) fields are preceded by a field-value length byte. With a length byte on every field, even FLOAT, CODED or BINARY fields, several instructions and one IF test are eliminated from the internal field scan loop. Having a length byte also allows some simple compression of BINARY, CODED, and FLOAT values.</td></tr>
<tr><th align="right"><var>X'80'</var></th><td>Enhanced Record Scan Files : All nonpreallocated (non-OCCURS) fields are preceded by a field-value length byte. With a length byte on every field, even FLOAT, CODED or BINARY fields, several instructions and one IF test are eliminated from the internal field scan loop. Having a length byte also allows some simple compression of BINARY, CODED, and FLOAT values.</td></tr>
<tr><th align="right"><var>X'40'</var></th><td>File skewing enabled. (This option is obsolete and no longer recommended by Rocket. See the Rocket <var class="product">Model&nbsp;204</var> File Manager's Guide for a discussion of its history.)</td></tr>
<tr><th align="right"><var>X'40'</var></th><td>File skewing enabled. (This option is obsolete and no longer recommended by Rocket. See the Rocket <var class="product">Model&nbsp;204</var> File Manager's Guide for a discussion of its history.)</td></tr>
<tr><th align="right"><var> X'20'</var></th><td>Unordered file.</td></tr>
<tr><th align="right"><var> X'20'</var></th><td>Unordered file.</td></tr>

Revision as of 03:20, 10 April 2013

Summary

Default value
0
Parameter type
File
Where set
During file creation
Related products
All
Introduced
Model 204 V6.1 or earlier

Description

The file (Table B) organization

Valid settings of FILEORG are:

SettingMeaning
X'100' Enhanced Data Handling Files:

Available in Model 204 V7.5.

Enables a number of enhancements to the file structure, including support for Repeating Field Groups (RFGs); the definition of up to 32000 fields in a file; system maintained Automatic fields; Field Constraints providing content validation; and improved space management of fields containing Large Objects.

If selected, the X'80' bit is automatically set.
X'80'Enhanced Record Scan Files : All nonpreallocated (non-OCCURS) fields are preceded by a field-value length byte. With a length byte on every field, even FLOAT, CODED or BINARY fields, several instructions and one IF test are eliminated from the internal field scan loop. Having a length byte also allows some simple compression of BINARY, CODED, and FLOAT values.
X'40'File skewing enabled. (This option is obsolete and no longer recommended by Rocket. See the Rocket Model 204 File Manager's Guide for a discussion of its history.)
X'20'Unordered file.
X'08'Hash Key File.
X'04'Reuse record number (RRN). This option can be added to any other FILEORG 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.

X'02'

Sort or hash key required in every record. (This option can be added to the X'08' and X'01' options.)
X'01'Sorted file.
X'00'Entry order file.