Initializing files - Revision history

JALWiccan: Automatically generated page update

2017-04-07T21:17:05Z

Automatically generated page update

← Older revision		Revision as of 21:17, 7 April 2017
Line 107:		Line 107:
	==Initializing record security files==		==Initializing record security files==
	<p>		<p>
	To initiate record security, set the X'20' option in the <var>OPENCTL</var> parameter in the <var>CREATE</var> command to indicate that record security is in effect. Record security is discussed in detail in [[~~Security~~#Record security\|Record security]]. The <var>INITIALIZE</var> command identifies the field that is to serve as the record security field. </p>		To initiate record security, set the X'20' option in the <var>OPENCTL</var> parameter in the <var>CREATE</var> command to indicate that record security is in effect. Record security is discussed in detail in [[Model 204 security features#Record security\|Record security]]. The <var>INITIALIZE</var> command identifies the field that is to serve as the record security field. </p>
	<p class="note"><b>Note:</b> Do not use the DEFINE command to define record security fields.</p>		<p class="note"><b>Note:</b> Do not use the DEFINE command to define record security fields.</p>

Line 140:		Line 140:
	</p>		</p>
	<p>		<p>
	Ensure that the value of <var class="term">m</var> is larger than the length allowed for <var>LOGIN</var> accounts (see [[~~Security~~#Record security\|Record security]]). Otherwise, if a user who has a long user ID attempts to store a record, <var class="product">Model 204</var> stores an empty record and cancels the user's request. The record is then inaccessible.</p>		Ensure that the value of <var class="term">m</var> is larger than the length allowed for <var>LOGIN</var> accounts (see [[Model 204 security features#Record security\|Record security]]). Otherwise, if a user who has a long user ID attempts to store a record, <var class="product">Model 204</var> stores an empty record and cancels the user's request. The record is then inaccessible.</p>

	[[Category:Model 204 files]]		[[Category:Model 204 files]]

ELowell: /* Initializing sort or hash key files */

2016-09-06T19:12:51Z

Initializing sort or hash key files

← Older revision		Revision as of 19:12, 6 September 2016
Line 52:		Line 52:
	To initialize a sort or hash key file (described in [[Sorted files]] and [[Hash key files]], respectively), issue the <var>INITIALIZE</var> command followed on the next line by <var>SORT</var> or <var>HASH</var>, along with a description of key fields.</p>		To initialize a sort or hash key file (described in [[Sorted files]] and [[Hash key files]], respectively), issue the <var>INITIALIZE</var> command followed on the next line by <var>SORT</var> or <var>HASH</var>, along with a description of key fields.</p>

	<p class="note"><b>Note:</b> Do not use the DEFINE command to define sort key ~~fields,~~ hash key ~~fields, or record security~~ fields.</p>		<p class="note"><b>Note:</b> Do not use the DEFINE command to define sort key or hash key fields.</p>

	===INITIALIZE command===		===INITIALIZE command===

ELowell: /* Initializing record security files */

2016-09-06T19:10:40Z

Initializing record security files

← Older revision		Revision as of 19:10, 6 September 2016
Line 108:		Line 108:
	<p>		<p>
	To initiate record security, set the X'20' option in the <var>OPENCTL</var> parameter in the <var>CREATE</var> command to indicate that record security is in effect. Record security is discussed in detail in [[Security#Record security\|Record security]]. The <var>INITIALIZE</var> command identifies the field that is to serve as the record security field. </p>		To initiate record security, set the X'20' option in the <var>OPENCTL</var> parameter in the <var>CREATE</var> command to indicate that record security is in effect. Record security is discussed in detail in [[Security#Record security\|Record security]]. The <var>INITIALIZE</var> command identifies the field that is to serve as the record security field. </p>
			<p class="note"><b>Note:</b> Do not use the DEFINE command to define record security fields.</p>

	====Syntax====		====Syntax====

ELowell: /* Initializing sort or hash key files */

2016-09-06T19:09:41Z

Initializing sort or hash key files

← Older revision		Revision as of 19:09, 6 September 2016
Line 51:		Line 51:
	<p>		<p>
	To initialize a sort or hash key file (described in [[Sorted files]] and [[Hash key files]], respectively), issue the <var>INITIALIZE</var> command followed on the next line by <var>SORT</var> or <var>HASH</var>, along with a description of key fields.</p>		To initialize a sort or hash key file (described in [[Sorted files]] and [[Hash key files]], respectively), issue the <var>INITIALIZE</var> command followed on the next line by <var>SORT</var> or <var>HASH</var>, along with a description of key fields.</p>

			<p class="note"><b>Note:</b> Do not use the DEFINE command to define sort key fields, hash key fields, or record security fields.</p>

	===INITIALIZE command===		===INITIALIZE command===
Line 102:		Line 104:
	<p>		<p>
	If keys are not required in each record, you cannot specify the <var>OCCURS</var> attribute. This allows <var class="product">Model 204</var> to distinguish between a missing key and a key that has a null value. See [[Field design#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information.</p>		If keys are not required in each record, you cannot specify the <var>OCCURS</var> attribute. This allows <var class="product">Model 204</var> to distinguish between a missing key and a key that has a null value. See [[Field design#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information.</p>

	==Initializing record security files==		==Initializing record security files==
	<p>		<p>

JAL at 21:20, 14 August 2014

2014-08-14T21:20:30Z

← Older revision		Revision as of 21:20, 14 August 2014
Line 16:		Line 16:

	====Always use the IN filename clause====		====Always use the IN filename clause====
	The above syntax shows the <var>[[IN clause in a command\|IN]]</var> <var class="term">filename</var> clause before the <var>INITIALIZE</var> command. Although this is, strictly speaking, an optional clause, its use is strongly recommended. Without it, the default file (that was most recently opened) is initialized, and sometimes the default file context is not the file which is intended to be initialized. This can result in severe unintentional effects; for example:		The above syntax shows the <var>[[Overview of Model 204 commands#IN: Specifying an IN clause in a command\|IN]]</var> <var class="term">filename</var> clause before the <var>INITIALIZE</var> command. Although this is, strictly speaking, an optional clause, its use is strongly recommended. Without it, the default file (that was most recently opened) is initialized, and sometimes the default file context is not the file which is intended to be initialized. This can result in severe unintentional effects; for example:
	<p class="code">* This example is <b>not</b> the recommended approach		<p class="code">* This example is <b>not</b> the recommended approach
	<nowiki>OPEN FILEA		<nowiki>OPEN FILEA

ELowell at 16:47, 12 May 2014

2014-05-12T16:47:15Z

← Older revision		Revision as of 16:47, 12 May 2014
Line 101:		Line 101:
	For more information, see [[Defining fields manually#OCCURS and LENGTH clauses\|OCCURS and LENGTH clauses]].		For more information, see [[Defining fields manually#OCCURS and LENGTH clauses\|OCCURS and LENGTH clauses]].
	<p>		<p>
	If keys are not required in each record, you cannot specify the <var>OCCURS</var> attribute. This allows <var class="product">Model 204</var> to distinguish between a missing key and a key that has a null value. See [[Field design ~~(File management)~~#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information.</p>		If keys are not required in each record, you cannot specify the <var>OCCURS</var> attribute. This allows <var class="product">Model 204</var> to distinguish between a missing key and a key that has a null value. See [[Field design#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information.</p>

	==Initializing record security files==		==Initializing record security files==

DmeWiccan: Automatically generated page update

2014-05-09T22:45:51Z

Automatically generated page update

← Older revision		Revision as of 22:45, 9 May 2014
Line 139:		Line 139:
	Ensure that the value of <var class="term">m</var> is larger than the length allowed for <var>LOGIN</var> accounts (see [[Security#Record security\|Record security]]). Otherwise, if a user who has a long user ID attempts to store a record, <var class="product">Model 204</var> stores an empty record and cancels the user's request. The record is then inaccessible.</p>		Ensure that the value of <var class="term">m</var> is larger than the length allowed for <var>LOGIN</var> accounts (see [[Security#Record security\|Record security]]). Otherwise, if a user who has a long user ID attempts to store a record, <var class="product">Model 204</var> stores an empty record and cancels the user's request. The record is then inaccessible.</p>

	[[Category:~~File management~~]]		[[Category:Model 204 files]]

JAL at 21:23, 17 April 2014

2014-04-17T21:23:52Z

← Older revision		Revision as of 21:23, 17 April 2014
Line 99:		Line 99:
	</ul>		</ul>

	For more information, see [[ Defining fields manually#OCCURS and LENGTH clauses\|OCCURS and LENGTH clauses]].		For more information, see [[Defining fields manually#OCCURS and LENGTH clauses\|OCCURS and LENGTH clauses]].
	<p>		<p>
	If keys are not required in each record, you cannot specify the <var>OCCURS</var> attribute. This allows <var class="product">Model 204</var> to distinguish between a missing key and a key that has a null value. See [[ Field design (File management)#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information.</p>		If keys are not required in each record, you cannot specify the <var>OCCURS</var> attribute. This allows <var class="product">Model 204</var> to distinguish between a missing key and a key that has a null value. See [[Field design (File management)#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information.</p>

	==Initializing record security files==		==Initializing record security files==

JALWiccan: Automatically generated page update

2014-04-17T20:59:19Z

Automatically generated page update

← Older revision		Revision as of 20:59, 17 April 2014
Line 101:		Line 101:
	For more information, see [[ Defining fields manually#OCCURS and LENGTH clauses\|OCCURS and LENGTH clauses]].		For more information, see [[ Defining fields manually#OCCURS and LENGTH clauses\|OCCURS and LENGTH clauses]].
	<p>		<p>
	If keys are not required in each record, you cannot specify the <var>OCCURS</var> attribute. This allows <var class="product">Model 204</var> to distinguish between a missing key and a key that has a null value. See [[ Field design (File management)#Preallocated fields\|Preallocated fields]] for more information.</p>		If keys are not required in each record, you cannot specify the <var>OCCURS</var> attribute. This allows <var class="product">Model 204</var> to distinguish between a missing key and a key that has a null value. See [[ Field design (File management)#Preallocated fields (OCCURS attribute)\|Preallocated fields]] for more information.</p>

	==Initializing record security files==		==Initializing record security files==

JAL: /* INITIALIZE command */

2014-02-24T21:14:30Z

INITIALIZE command

← Older revision		Revision as of 21:14, 24 February 2014
Line 63:		Line 63:
	<p><var class="term">fieldname</var> is the name of the sort or hash key field, followed by a list of field attributes.		<p><var class="term">fieldname</var> is the name of the sort or hash key field, followed by a list of field attributes.

	For example, the following commands ~~identifies~~ the IDENT field as having the KEY and FRV attributes:</p>		For example, the following commands identify the <code>IDENT</code> field as having the <var>KEY</var> and <var>FRV</var> attributes:</p>
	<p class="code">OPEN CARS		<p class="code">OPEN CARS
	IN <var class="term">filename</var> INITIALIZE		IN <var class="term">filename</var> INITIALIZE
Line 69:		Line 69:
	</p>		</p>
	<p>		<p>
	Specify as many field attributes as needed. For a complete listing of field attributes, see [[ Defining fields manually#Defining fields\|Defining fields]]. The complete syntax and description of INITIALIZE is located on the [[INITIALIZE command]] page.</p>		Specify as many field attributes as needed. For a complete listing of field attributes, see [[ Defining fields manually#Defining fields\|Defining fields]]. The complete syntax and description of <var>INITIALIZE</var> is located on the [[INITIALIZE command]] page.</p>
	<p>		<p>
	The non-resettable [[FPARMS and TABLES file parameters#File characteristics parameters (FPARMS)\|FPARMS]] parameters <var>[[SORTKEY_parameter\|SORTKEY]]</var> and <var>[[HASHKEY_parameter\|HASHKEY]]</var> are set based on the command values.</p>		The non-resettable [[FPARMS and TABLES file parameters#File characteristics parameters (FPARMS)\|FPARMS]] parameters <var>[[SORTKEY_parameter\|SORTKEY]]</var> and <var>[[HASHKEY_parameter\|HASHKEY]]</var> are set based on the command values.</p>

	===Sort and hash key file restrictions===		===Sort and hash key file restrictions===
	<p>		<p>