Defining fields manually - Revision history

JAL: link repair

2017-04-07T21:21:10Z

link repair

← Older revision		Revision as of 21:21, 7 April 2017
Line 328:		Line 328:
	</td>		</td>
	<td>		<td>
	See [[~~Security~~]]		See [[Model 204 security features]]
	</td>		</td>
	</tr>		</tr>

JAL: add 7.5 attributes

2015-03-31T16:12:27Z

add 7.5 attributes

@@ Line 198: / Line 198: @@
 <th>Abbreviation</th>
 <th>Default</th>
 </tr>
@@ Line 250: / Line 240: @@
 </tr>
 <tr>
 <td>
@@ Line 282: / Line 294: @@
 </tr>
 </table>
 ====Field constraints====
 <p>

JAL: formatting tweak

2015-03-24T19:18:48Z

formatting tweak

← Older revision		Revision as of 19:18, 24 March 2015
Line 516:		Line 516:

	<p>		<p>
	See [[Setting up the date-time stamp field]] for the steps the System Manger must take before this feature is used, <br>		See [[Setting up the date-time stamp field]] for the steps the System Manger must take before this feature is used.
	~~and~~ [[Adding a date-time stamp field]] for rules on using the feature.</p>		</p>
			<p>
			See [[Adding a date-time stamp field]] for rules about using the date-time stamp feature.</p>

	==Preventing definition of new field names==		==Preventing definition of new field names==
	<p>		<p>

ELowell at 16:59, 12 May 2014

2014-05-12T16:59:19Z

← Older revision		Revision as of 16:59, 12 May 2014
Line 26:		Line 26:
	<li><var class="term">attribute</var> is a member of the list in [[Field attributes]].		<li><var class="term">attribute</var> is a member of the list in [[Field attributes]].
	<p>		<p>
	If you specify the ORDERED attribute, you can follow it with a list of qualifying parameters that designate the type of ordering and the space utilization characteristics of the Ordered Index. See the discussion of the ORDERED attribute in [[ Field design ~~(File management)~~#ORDERED and NON-ORDERED attributes\|ORDERED and NON-ORDERED attributes]]. </p></li>		If you specify the ORDERED attribute, you can follow it with a list of qualifying parameters that designate the type of ordering and the space utilization characteristics of the Ordered Index. See the discussion of the ORDERED attribute in [[ Field design#ORDERED and NON-ORDERED attributes\|ORDERED and NON-ORDERED attributes]]. </p></li>
	</ul>		</ul>

Line 56:		Line 56:
	===Field attributes===		===Field attributes===
	<p>		<p>
	The attributes listed in the following tables are introduced in [[Field design ~~(File management)~~\|Field design]], along with a summary of the rules follow in assigning them. A number of the attributes have additional optional attributes (in particular, see [[Field design ~~(File management)~~#ORDERED field definition\|the ORDERED attribute]]) that can be specified with the [[DEFINE FIELD command]], which are also described in [[Field design ~~(File management)~~\|Field design]].</p>		The attributes listed in the following tables are introduced in [[Field design\|Field design]], along with a summary of the rules follow in assigning them. A number of the attributes have additional optional attributes (in particular, see [[Field design#ORDERED field definition\|the ORDERED attribute]]) that can be specified with the [[DEFINE FIELD command]], which are also described in [[Field design\|Field design]].</p>

	====Indexing attributes====		====Indexing attributes====

DmeWiccan: Automatically generated page update

2014-05-09T22:45:38Z

Automatically generated page update

← Older revision		Revision as of 22:45, 9 May 2014
Line 527:		Line 527:
	Regardless of the setting of the <var>FOPT</var> parameter, users with file manager privileges (see the <var>[[PRIVDEF parameter\|PRIVDEF]]</var> parameter) can define new fields at any time. See the [[FOPT parameter]] discussion for more detail. </p>		Regardless of the setting of the <var>FOPT</var> parameter, users with file manager privileges (see the <var>[[PRIVDEF parameter\|PRIVDEF]]</var> parameter) can define new fields at any time. See the [[FOPT parameter]] discussion for more detail. </p>

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

JAL at 01:08, 30 January 2014

2014-01-30T01:08:48Z

← Older revision		Revision as of 01:08, 30 January 2014
Line 1:		Line 1:
	<p>		<p>
	This chapter describes the use of [[DEFINE FIELD command]], which allows you to define the fields in a file. For the full syntax, follow that link.</p>		This chapter describes the use of the <var>[[DEFINE FIELD command\|DEFINE FIELD]]</var> command, which allows you to define the fields in a file. For the full syntax, follow that link.</p>

	==Defining fields==		==Defining fields==
	<p>		<p>
	After you <var>[[CREATE command: File\|CREATE]]</var> and <var>[[INITIALIZE command\|INITIALIZE]]</var> a <var class="product">Model 204</var> file, use the DEFINE command or the IFDFLD Host Language Interface function to establish the names and types of the fields in the file. </p>		After you <var>[[CREATE command: File\|CREATE]]</var> and <var>[[INITIALIZE command\|INITIALIZE]]</var> a <var class="product">Model 204</var> file, use the DEFINE command or the IFDFLD Host Language Interface function to establish the names and types of the fields in the file. </p>

			<b>Syntax</b>
	<p>		<p>
	The format of the DEFINE command is:</p>		The format of the DEFINE command is:</p>
	~~<b>Syntax</b>~~
	<p class="code">DEFINE FIELD <var class="term">name</var> [(<var class="term">attribute</var> [,[<var class="term">attribute</var> ...]]) \|		<p class="code">DEFINE FIELD <var class="term">name</var> [(<var class="term">attribute</var> [,[<var class="term">attribute</var> ...]]) \|
	WITH [<var class="term">attribute</var>][,[<var class="term">attribute</var> ...]]]		WITH [<var class="term">attribute</var>][,[<var class="term">attribute</var> ...]]]
Line 15:		Line 16:
	<ul>		<ul>
	<li><var class="term">name</var> is a 1 to 255 character name that must begin with a letter and can contain any alphanumeric characters, including spaces, except:		<li><var class="term">name</var> is a 1 to 255 character name that must begin with a letter and can contain any alphanumeric characters, including spaces, except:
	<p class="code">??		<p class="code"><b>??
	?$		?$
	?&		?&
	@ (or an alternative delete character)		@</b> (or an alternative delete character)
	<b></b># (or an alternative flush character)		<b>#</b> (or an alternative flush character)
	;		<b>;</b>
	</p></li>		</p></li>

Line 520:		Line 521:
	==Preventing definition of new field names==		==Preventing definition of new field names==
	<p>		<p>
	<var class="product">Model 204</var> permits a user to define new fields at any time. This is an advantage in some applications, because it enables the file to evolve beyond its original definition. If your site does not want users to add new field names, reset the FOPT parameter to X'01' from its default value of X'00'. This file option causes <var class="product">Model 204</var> to issue the following response, when a user issues a DEFINE command:</p>		<var class="product">Model 204</var> permits a user to define new fields at any time. This is an advantage in some applications, because it enables the file to evolve beyond its original definition. If your site does not want users to add new field names, reset the <var>[[FOPT parameter\|FOPT]]</var> parameter to X'01' from its default value of X'00'. This file option causes <var class="product">Model 204</var> to issue the following response, when a user issues a DEFINE command:</p>
	<p class="code"><b></b>*** M204.1261: NEW FIELD NAMES NOT PERMITTED		<p class="code"><b></b>*** M204.1261: NEW FIELD NAMES NOT PERMITTED
	</p>		</p>
	<p>		<p>
	Regardless of the setting of the [[FOPT parameter]], users with file manager privileges (see the [[PRIVDEF parameter]]) can define new fields at any time. See the ~~discussion in~~ [[FOPT parameter]] for more detail. </p>		Regardless of the setting of the <var>FOPT</var> parameter, users with file manager privileges (see the <var>[[PRIVDEF parameter\|PRIVDEF]]</var> parameter) can define new fields at any time. See the [[FOPT parameter]] discussion for more detail. </p>

	[[Category:File management]]		[[Category:File management]]

JAL at 00:57, 30 January 2014

2014-01-30T00:57:37Z

Show changes

JAL at 20:53, 2 January 2014

2014-01-02T20:53:45Z

← Older revision		Revision as of 20:53, 2 January 2014
Line 16:		Line 16:
	;		;
	</p>		</p>
	<p>attribute is a member of the list in [[~~Field Attributes\|~~Field attributes]]. </p>		<p>attribute is a member of the list in [[Field attributes]]. </p>
	<p>If you specify the ORDERED attribute, you can follow it with a list of qualifying parameters that designate the type of ordering and the space utilization characteristics of the Ordered Index. See the discussion of the ORDERED attribute in [[ Field design (File management)#ORDERED and NON-ORDERED attributes\|ORDERED and NON-ORDERED attributes]]. </p>		<p>If you specify the ORDERED attribute, you can follow it with a list of qualifying parameters that designate the type of ordering and the space utilization characteristics of the Ordered Index. See the discussion of the ORDERED attribute in [[ Field design (File management)#ORDERED and NON-ORDERED attributes\|ORDERED and NON-ORDERED attributes]]. </p>
	<b>Example</b>		<b>Example</b>
Line 22:		Line 22:
	<p class="code">DEFINE FIELD CUSTID ORDERED CHARACTER		<p class="code">DEFINE FIELD CUSTID ORDERED CHARACTER
	</p>		</p>
	<p>Specify as many field attributes as needed from [[~~Field Attributes\|~~Field attributes]]. For each attribute pair shown in the list, only one of the alternatives can be specified; conflicting attributes, such as KEY and NON-KEY, cannot be used together in a single description.</p>		<p>Specify as many field attributes as needed from [[Field attributes]]. For each attribute pair shown in the list, only one of the alternatives can be specified; conflicting attributes, such as KEY and NON-KEY, cannot be used together in a single description.</p>
	<p class="note"><b>Note:</b>		<p class="note"><b>Note:</b>
	Every attribute has a default value. Therefore, you only need to specify the attribute if it is not the default.</p>		Every attribute has a default value. Therefore, you only need to specify the attribute if it is not the default.</p>

ELowell at 23:42, 16 December 2013

2013-12-16T23:42:42Z

← Older revision		Revision as of 23:42, 16 December 2013
Line 444:		Line 444:
	<p>The date-time stamp feature in <var class="product">Model 204</var> lets you can easily discern when a record in a file was last changed. The date-time stamp feature is supported for ONLINE and BATCH204.</p>		<p>The date-time stamp feature in <var class="product">Model 204</var> lets you can easily discern when a record in a file was last changed. The date-time stamp feature is supported for ONLINE and BATCH204.</p>

	<p>See [[Setting up the ~~Date~~-~~Time Stamp~~ field]] for the steps the System Manger must take before this feature is used, <br>		<p>See [[Setting up the date-time stamp field]] for the steps the System Manger must take before this feature is used, <br>
	and [[Adding a date-time stamp field]] for rules on using the feature.</p>		and [[Adding a date-time stamp field]] for rules on using the feature.</p>

ELowell at 20:11, 16 December 2013

2013-12-16T20:11:39Z

← Older revision		Revision as of 20:11, 16 December 2013
Line 17:		Line 17:
	</p>		</p>
	<p>attribute is a member of the list in [[Field Attributes\|Field attributes]]. </p>		<p>attribute is a member of the list in [[Field Attributes\|Field attributes]]. </p>
	<p>If you specify the ORDERED attribute, you can follow it with a list of qualifying parameters that designate the type of ordering and the space utilization characteristics of the Ordered Index. See the discussion of the ORDERED attribute in [[ Field ~~Design~~ (File ~~Management~~)#ORDERED and NON-ORDERED attributes\|ORDERED and NON-ORDERED attributes]]. </p>		<p>If you specify the ORDERED attribute, you can follow it with a list of qualifying parameters that designate the type of ordering and the space utilization characteristics of the Ordered Index. See the discussion of the ORDERED attribute in [[ Field design (File management)#ORDERED and NON-ORDERED attributes\|ORDERED and NON-ORDERED attributes]]. </p>
	<b>Example</b>		<b>Example</b>
	<p>In the following example the field CUSTID is named and given the ORDERED CHARACTER attribute:</p>		<p>In the following example the field CUSTID is named and given the ORDERED CHARACTER attribute:</p>
Line 39:		Line 39:

	===Field attributes===		===Field attributes===
	<p>The attributes listed in the following tables are introduced in [[Field ~~Design~~ (File ~~Management~~)\|Field ~~Design~~]], along with a summary of the rules follow in assigning them. A number of the attributes have additional optional attributes (in particular, see [[Field ~~Design~~ (File ~~Management~~)#ORDERED field definition\|the ORDERED attribute]]) that can be specified with the [[DEFINE FIELD command]], which are also described in [[Field ~~Design~~ (File ~~Management~~)\|Field ~~Design~~]].</p>		<p>The attributes listed in the following tables are introduced in [[Field design (File management)\|Field design]], along with a summary of the rules follow in assigning them. A number of the attributes have additional optional attributes (in particular, see [[Field design (File management)#ORDERED field definition\|the ORDERED attribute]]) that can be specified with the [[DEFINE FIELD command]], which are also described in [[Field design (File management)\|Field design]].</p>

	====Indexing attributes====		====Indexing attributes====