Creating a file with FILEMGMT - Revision history

ELowell: /* Defining file organization */

2016-09-26T20:29:25Z

Defining file organization

← Older revision		Revision as of 20:29, 26 September 2016
Line 89:		Line 89:
	<li>In the <b>Filename</b> input field, enter the name of the file that you are creating.		<li>In the <b>Filename</b> input field, enter the name of the file that you are creating.
	<p>		<p>
	The name can be as many as eight characters long (7 for DOS systems). The file name cannot be <code>FILE</code> or <code>GROUP</code> and cannot start with <code>CCA</code>, <code>SYS</code>, <code>OUT</code>, <code>TAPE</code>, or a number. It ~~must start with an uppercase letter, and~~ can contain only uppercase letters, numbers, and the following special characters:</p>		The name can be as many as eight characters long (7 for DOS systems). The file name cannot be <code>FILE</code> or <code>GROUP</code> and cannot start with <code>CCA</code> (except for [[System requirements for Application Subsystems#Creating CCASYS\|CCASYS]]), <code>SYS</code>, <code>OUT</code>, <code>TAPE</code>, or a number. It can contain only uppercase letters, numbers, and the following special characters:</p>
	<ul>		<ul>
	<li>At sign (<tt>@</tt>)</li>		<li>At sign (<tt>@</tt>)</li>

ELowell: /* Defining file organization */

2016-09-26T19:08:43Z

Defining file organization

← Older revision		Revision as of 19:08, 26 September 2016
Line 89:		Line 89:
	<li>In the <b>Filename</b> input field, enter the name of the file that you are creating.		<li>In the <b>Filename</b> input field, enter the name of the file that you are creating.
	<p>		<p>
	The name can be as many as eight characters long. The file name cannot be <code>FILE</code> or <code>GROUP</code> and cannot start with <code>CCA</code>, <code>SYS</code>, <code>OUT</code>, <code>TAPE</code>, or a number. It must start with a letter, and can contain only letters, numbers, and the following special characters:</p>		The name can be as many as eight characters long (7 for DOS systems). The file name cannot be <code>FILE</code> or <code>GROUP</code> and cannot start with <code>CCA</code>, <code>SYS</code>, <code>OUT</code>, <code>TAPE</code>, or a number. It must start with an uppercase letter, and can contain only uppercase letters, numbers, and the following special characters:</p>
	<ul>		<ul>
	<li>At sign (<tt>@</tt>)</li>		<li>At sign (<tt>@</tt>)</li>
	<li>Pound sign (<tt>#</tt>)</li>		<li>Pound sign (<tt>#</tt>)</li>
	<li>Dollar sign (<tt>$</tt>)</li>		<li>Dollar sign (<tt>$</tt>) (alternately displayed as £)</li>
	</ul>		</ul>

JAL: /* Defining file organization */ typo

2015-07-24T20:27:08Z

Defining file organization: typo

← Older revision		Revision as of 20:27, 24 July 2015
Line 40:		Line 40:
	<li>Select the FILE Maintenance CREATE function (number 1) from the primary screen.		<li>Select the FILE Maintenance CREATE function (number 1) from the primary screen.
	<p>		<p>
	FILEMGMT displays the first of the three File Definition screens, the Organization ~~Screen~~:</p>		FILEMGMT displays the first of the three File Definition screens, the Organization screen:</p>
	</li>		</li>
	</ol>		</ol>

Dme at 04:57, 10 May 2014

2014-05-10T04:57:41Z

← Older revision		Revision as of 04:57, 10 May 2014
Line 5:		Line 5:
	<li>You must have Dictionary/204 and its subsystems running in order to use FILEMGMT.</li>		<li>You must have Dictionary/204 and its subsystems running in order to use FILEMGMT.</li>

	<li>Before working your way through the File Management Subsystem facility (FILEMGMT) interface to create a file, you should have made decisions about the organization, recovery options, and security for the file you are creating. See [[File design ~~(File management)~~]] for more information.</li>		<li>Before working your way through the File Management Subsystem facility (FILEMGMT) interface to create a file, you should have made decisions about the organization, recovery options, and security for the file you are creating. See [[File design]] for more information.</li>
	</ul>		</ul>
	</blockquote>		</blockquote>
Line 119:		Line 119:
	<li>In the <b>Opt Fld Ext</b> (optimized field extract) input field, enter <code>Y</code> to add a length byte to every non-preallocated (or non-<var>OCCURS</var>) field, which could result in faster field extraction. The improvement is most noticeable when you have built records with a large number of fields. Entering <code>Y</code> sets <var>FILEORG</var> to X'80'.		<li>In the <b>Opt Fld Ext</b> (optimized field extract) input field, enter <code>Y</code> to add a length byte to every non-preallocated (or non-<var>OCCURS</var>) field, which could result in faster field extraction. The improvement is most noticeable when you have built records with a large number of fields. Entering <code>Y</code> sets <var>FILEORG</var> to X'80'.
	<p>		<p>
	The default is <code>N</code>: non-preallocated (or non-<var>OCCURS</var>) fields that are type <var>FLOAT</var>, <var>CODED</var>, and <var>BINARY</var> are not stored with a preceding length byte. See [[Field design ~~(File management)~~#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information on preallocated and non-preallocated fields.</p>		The default is <code>N</code>: non-preallocated (or non-<var>OCCURS</var>) fields that are type <var>FLOAT</var>, <var>CODED</var>, and <var>BINARY</var> are not stored with a preceding length byte. See [[Field design#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information on preallocated and non-preallocated fields.</p>
	</li>		</li>

Line 128:		Line 128:
	<li>In the <b>LG Files</b> input field, enter <code>Y</code> to enable support for large files. Large files, available in Model 204 version 7.5, can hold up to 48 million records. Entering <code>Y</code> sets <var>FILEORG</var> to X'200'.		<li>In the <b>LG Files</b> input field, enter <code>Y</code> to enable support for large files. Large files, available in Model 204 version 7.5, can hold up to 48 million records. Entering <code>Y</code> sets <var>FILEORG</var> to X'200'.

	<li>In the <b>FILE ORGANIZATION</b> section, select file organization characteristics for the specified file. FILEMGMT computes the <var class="product">Model 204</var> <var>[[FILEORG parameter\|FILEORG]]</var> parameter from your selections and displays the computed value. See [[File design ~~(File management)~~]] for details on the advantages and disadvantages of each file organization type.		<li>In the <b>FILE ORGANIZATION</b> section, select file organization characteristics for the specified file. FILEMGMT computes the <var class="product">Model 204</var> <var>[[FILEORG parameter\|FILEORG]]</var> parameter from your selections and displays the computed value. See [[File design]] for details on the advantages and disadvantages of each file organization type.
	<ol class="low-al">		<ol class="low-al">
	<li>Select one of the following options:		<li>Select one of the following options:

DmeWiccan: Automatically generated page update

2014-05-10T04:20:50Z

Automatically generated page update

← Older revision		Revision as of 04:20, 10 May 2014
Line 335:		Line 335:
	You can select the Size function to resize the file after you redefine the file on the Definition screens. </p>		You can select the Size function to resize the file after you redefine the file on the Definition screens. </p>

	~~[[Category:Model 204 files]]~~
	[[Category:FILEMGMT application subsystem]]		[[Category:FILEMGMT application subsystem]]

DmeWiccan: Automatically generated page update

2014-05-09T22:45:35Z

Automatically generated page update

← Older revision		Revision as of 22:45, 9 May 2014
Line 335:		Line 335:
	You can select the Size function to resize the file after you redefine the file on the Definition screens. </p>		You can select the Size function to resize the file after you redefine the file on the Definition screens. </p>

	[[Category:~~File management~~]]		[[Category:Model 204 files]]
	[[Category:FILEMGMT application subsystem]]		[[Category:FILEMGMT application subsystem]]

JAL at 21:18, 17 April 2014

2014-04-17T21:18:45Z

← Older revision		Revision as of 21:18, 17 April 2014
Line 119:		Line 119:
	<li>In the <b>Opt Fld Ext</b> (optimized field extract) input field, enter <code>Y</code> to add a length byte to every non-preallocated (or non-<var>OCCURS</var>) field, which could result in faster field extraction. The improvement is most noticeable when you have built records with a large number of fields. Entering <code>Y</code> sets <var>FILEORG</var> to X'80'.		<li>In the <b>Opt Fld Ext</b> (optimized field extract) input field, enter <code>Y</code> to add a length byte to every non-preallocated (or non-<var>OCCURS</var>) field, which could result in faster field extraction. The improvement is most noticeable when you have built records with a large number of fields. Entering <code>Y</code> sets <var>FILEORG</var> to X'80'.
	<p>		<p>
	The default is <code>N</code>: non-preallocated (or non-<var>OCCURS</var>) fields that are type <var>FLOAT</var>, <var>CODED</var>, and <var>BINARY</var> are not stored with a preceding length byte. See [[File ~~size calculation~~#Preallocated fields\|Preallocated fields]] for more information on preallocated and non-preallocated fields.</p>		The default is <code>N</code>: non-preallocated (or non-<var>OCCURS</var>) fields that are type <var>FLOAT</var>, <var>CODED</var>, and <var>BINARY</var> are not stored with a preceding length byte. See [[Field design (File management)#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information on preallocated and non-preallocated fields.</p>
	</li>		</li>

JAL at 21:11, 17 April 2014

2014-04-17T21:11:36Z

← Older revision		Revision as of 21:11, 17 April 2014
Line 119:		Line 119:
	<li>In the <b>Opt Fld Ext</b> (optimized field extract) input field, enter <code>Y</code> to add a length byte to every non-preallocated (or non-<var>OCCURS</var>) field, which could result in faster field extraction. The improvement is most noticeable when you have built records with a large number of fields. Entering <code>Y</code> sets <var>FILEORG</var> to X'80'.		<li>In the <b>Opt Fld Ext</b> (optimized field extract) input field, enter <code>Y</code> to add a length byte to every non-preallocated (or non-<var>OCCURS</var>) field, which could result in faster field extraction. The improvement is most noticeable when you have built records with a large number of fields. Entering <code>Y</code> sets <var>FILEORG</var> to X'80'.
	<p>		<p>
	The default is <code>N</code>: non-preallocated (or non-<var>OCCURS</var>) fields that are type <var>FLOAT</var>, <var>CODED</var>, and <var>BINARY</var> are not stored with a preceding length byte. See [[File size calculation#Preallocated fields ~~(OCCURS attribute)~~\|Preallocated fields]] for more information on preallocated and non-preallocated fields.</p>		The default is <code>N</code>: non-preallocated (or non-<var>OCCURS</var>) fields that are type <var>FLOAT</var>, <var>CODED</var>, and <var>BINARY</var> are not stored with a preceding length byte. See [[File size calculation#Preallocated fields\|Preallocated fields]] for more information on preallocated and non-preallocated fields.</p>
	</li>		</li>

JALWiccan: Automatically generated page update

2014-04-17T20:57:50Z

Automatically generated page update

← Older revision		Revision as of 20:57, 17 April 2014
Line 119:		Line 119:
	<li>In the <b>Opt Fld Ext</b> (optimized field extract) input field, enter <code>Y</code> to add a length byte to every non-preallocated (or non-<var>OCCURS</var>) field, which could result in faster field extraction. The improvement is most noticeable when you have built records with a large number of fields. Entering <code>Y</code> sets <var>FILEORG</var> to X'80'.		<li>In the <b>Opt Fld Ext</b> (optimized field extract) input field, enter <code>Y</code> to add a length byte to every non-preallocated (or non-<var>OCCURS</var>) field, which could result in faster field extraction. The improvement is most noticeable when you have built records with a large number of fields. Entering <code>Y</code> sets <var>FILEORG</var> to X'80'.
	<p>		<p>
	The default is <code>N</code>: non-preallocated (or non-<var>OCCURS</var>) fields that are type <var>FLOAT</var>, <var>CODED</var>, and <var>BINARY</var> are not stored with a preceding length byte. See [[File size calculation#Preallocated fields\|Preallocated fields]] for more information on preallocated and non-preallocated fields.</p>		The default is <code>N</code>: non-preallocated (or non-<var>OCCURS</var>) fields that are type <var>FLOAT</var>, <var>CODED</var>, and <var>BINARY</var> are not stored with a preceding length byte. See [[File size calculation#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information on preallocated and non-preallocated fields.</p>
	</li>		</li>

JAL: /* Defining file organization */

2014-04-03T20:15:41Z

Defining file organization

← Older revision		Revision as of 20:15, 3 April 2014
Line 313:		Line 313:
	</table></li>		</table></li>

	<li><b>Format File During CREATE:</b> FILEMGMT formats the file during file creation. Valid values are Y and N. Rocket Software recommends that you use the default value, Y, in order to maintain file integrity.</li>		<li><b>Format File During CREATE:</b> FILEMGMT formats the file during file creation. Valid values are <code>Y</code> and <code>N</code>. Rocket Software recommends that you use the default value, <code>Y</code>, in order to maintain file integrity.</li>

	<li><b>Verify Disk Updates:</b> FILEMGMT verifies all updates made to the file during file creation. Valid values are Y and N. Rocket Software recommends that you use the default value, N. The computer does its own verification of disk updates, so this option is no longer necessary and likely to cause overhead.</li>		<li><b>Verify Disk Updates:</b> FILEMGMT verifies all updates made to the file during file creation. Valid values are <code>Y</code> and <code>N</code>. Rocket Software recommends that you use the default value, <code>N</code>. The computer does its own verification of disk updates, so this option is no longer necessary and likely to cause overhead.</li>
	</ol>		</ol>