Defining fields manually: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (link repair)
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<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>
<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>After you <var>[[CREATE command: File|CREATE]]</var> and <var>[[INITIALIZE command|INITIALIZE]]</var> a <var class="product">Model&nbsp;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>
<p>
<p>The format of the DEFINE command is:</p>
After you <var>[[CREATE command: File|CREATE]]</var> and <var>[[INITIALIZE command|INITIALIZE]]</var> a <var class="product">Model&nbsp;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>
<b>Syntax</b>
<p>
The format of the DEFINE command is:</p>
<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> ...]]]
</p>
</p>
<p>where:</p>
<p>
<p>name is a 1 to 255 character name that must begin with a letter and can contain any alphanumeric characters, including spaces, except:</p>
where:</p>
<p class="code">??
<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:
<p class="code"><b>??
?$
?$
?&amp;
?&amp;
@ (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>
</p></li>
<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>
<li><var class="term">attribute</var> is a member of the list in [[Field attributes]].  
<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#ORDERED and NON-ORDERED attributes|ORDERED and NON-ORDERED attributes]].  </p></li>
</ul>
 
<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>
<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>
<p class="note"><b>Note:</b>  
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>
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>
 
===When to use the FIELD keyword===
===When to use the FIELD keyword===
<p>The keyword FIELD is required before field names that begin with the word FIELD, PRINTER, or DATASET. It is optional with other field names. If FIELD is specified, only one field can be defined or redefined per command. For example:</p>
<p>
The keyword FIELD is required before field names that begin with the word FIELD, PRINTER, or DATASET. It is optional with other field names. If FIELD is specified, only one field can be defined or redefined per command. For example:</p>
<p class="code">DEFINE FIELD POLICYHOLDER
<p class="code">DEFINE FIELD POLICYHOLDER
DEFINE POLICYHOLDER
DEFINE POLICYHOLDER
</p>
</p>
<p>Each example above defines a field with the name POLICYHOLDER. The following example defines a field with the name FIELD LOCATION:</p>
<p>
Each example above defines a field with the name POLICYHOLDER. The following example defines a field with the name FIELD LOCATION:</p>
<p class="code">DEFINE FIELD FIELD LOCATION
<p class="code">DEFINE FIELD FIELD LOCATION
</p>
</p>
 
===Defining sort key, hash key, and record security fields===
===Defining sort key, hash key, and record security fields===
<p>The DEFINE command cannot be used to define sort key fields, hash key fields, or record security fields. These fields can be defined only with the <var>[[INITIALIZE command|INITIALIZE]]</var> command and the appropriate parameter settings.</p>
<p>
 
The DEFINE command cannot be used to define sort key fields, hash key fields, or record security fields. These fields can be defined only with the <var>[[INITIALIZE command|INITIALIZE]]</var> command and the appropriate parameter settings.</p>
===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|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====
 
<p>
<p>The overall effect of the defaults is that, unless specified, the field is not indexed.</p>  
The overall effect of the defaults is that, unless specified, the field is not indexed.</p>
 
<table>
<table>
<caption>Indexing field attributes with the DEFINE command</caption>
<caption>Indexing field attributes with the DEFINE command</caption>
Line 50: Line 67:
<th>Attribute</th><th>Abbreviation</th><th>Default</th>
<th>Attribute</th><th>Abbreviation</th><th>Default</th>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 59: Line 77:
<td>NON-ORDERED</td>
<td>NON-ORDERED</td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 68: Line 87:
<td>NON-ORDERED</td>
<td>NON-ORDERED</td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 77: Line 97:
<td>NON-KEY</td>
<td>NON-KEY</td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 87: Line 108:
<td>NON-FRV</td>
<td>NON-FRV</td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 98: Line 120:
</tr>
</tr>
</table>
</table>
 
====Data types====
====Data types====
<p>
<p>
In most cases, only one of these may be specified on any field (see the UTF attributes). The default is STRING</p>
In most cases, only one of these may be specified on any field (see the UTF attributes). The default is STRING</p>
 
<table>
<table>
<caption>Data type attributes with the DEFINE command</caption>
<caption>Data type attributes with the DEFINE command</caption>
Line 110: Line 132:
<th>Notes</th>
<th>Notes</th>
</tr>
</tr>
<tr>
<tr>
<td>STRING</td>
<td>STRING</td>
Line 115: Line 138:
<td></td>
<td></td>
</tr>
</tr>
<tr>
<tr>
<td>BINARY</td>
<td>BINARY</td>
Line 120: Line 144:
<td></td>
<td></td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 131: Line 156:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td>FLOAT</td>
<td>FLOAT</td>
Line 136: Line 162:
<td>Must have LEN specified</td>
<td>Must have LEN specified</td>
</tr>
</tr>
<tr>
<tr>
<td>DATETIME</td>
<td>DATETIME</td>
Line 141: Line 168:
<td></td>
<td></td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 152: Line 180:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 161: Line 190:
</tr>
</tr>
</table>
</table>
 
==== Data content attributes====
==== Data content attributes====
<table>
<table>
Line 170: Line 199:
<th>Default</th>
<th>Default</th>
</tr>
</tr>
<tr>
<td>
UPDATE IN PLACE<p>UPDATE AT END</p>
</td>
<td>
UP<p>UE</p>
</td>
<td>UPDATE IN PLACE</td>
</tr>
<tr>
<tr>
<td>
<td>
Line 190: Line 211:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td>OCCURS n</td>
<td>OCCURS n</td>
Line 195: Line 217:
<td>No preallocated occurrences</td>
<td>No preallocated occurrences</td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 206: Line 229:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 215: Line 239:
<td>DEFERRABLE</td>
<td>DEFERRABLE</td>
</tr>
</tr>
<tr>
<td>
UPDATE IN PLACE<p>UPDATE AT END</p>
</td>
<td>
UP<p>UE</p>
</td>
<td>UPDATE IN PLACE</td>
</tr>
<tr>
<td>DEFAULT-VALUE
<p>STORE-DEFAULT</p>
<p>STORE-NULL</p></td>
<td>DV
<p>SD</p>
<p>SN</p></td>
<td>&nbsp;
<p>LITERAL</p>
<p>LITERAL</p></td>
</tr>
<tr>
<tr>
<td>
<td>
Line 226: Line 273:
<td>REPT (except in 1NF files), or inside a field group (where it is EXONE)<p></p><p></p></td>
<td>REPT (except in 1NF files), or inside a field group (where it is EXONE)<p></p><p></p></td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 235: Line 283:
<td>NON-CODED</td>
<td>NON-CODED</td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 246: Line 295:
</table>
</table>


==== Field constraints ====
====Field constraints====
<p>More than one constraint may be set on a field. For example, if you only want to accept integer values between 5 and 99, then you can code:</p>
<p>
 
More than one constraint may be set on a field. For example, if you only want to accept integer values between 5 and 99, then you can code:</p>
<p class="code">DEFINE FIELD ''fieldname'' WITH INTGE 5 INTLE 99  
<p class="code">DEFINE FIELD <i>fieldname</i> WITH INTGE 5 INTLE 99
</p>
</p>
 
<table>
<table>
<caption>Field constraint attributes with DEFINE command</caption>
<caption>Field constraint attributes with DEFINE command</caption>
Line 259: Line 309:
<th>Notes</th>
<th>Notes</th>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 268: Line 319:
<td>NON-UNIQUE is default</td>
<td>NON-UNIQUE is default</td>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 276: Line 328:
</td>
</td>
<td>
<td>
See [[Security]]
See [[Model 204 security features]]
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td colspan="3">
<td colspan="3">
Line 284: Line 337:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td>LENGTH-EQ</td><td>LEQ</td><td>Available as of V7.5</td>
<td>LENGTH-EQ</td><td>LEQ</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>LENGTH-GE</td><td>LGE</td><td>Available as of V7.5</td>
<td>LENGTH-GE</td><td>LGE</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>LENGTH-LE</td><td>LLE</td><td>Available as of V7.5</td>
<td>LENGTH-LE</td><td>LLE</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td colspan="3">
<td colspan="3">
Line 299: Line 356:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td>INTEGER-GE</td><td>INTGE</td><td>Available as of V7.5</td>
<td>INTEGER-GE</td><td>INTGE</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>INTEGER-GT</td><td>INTGT</td><td>Available as of V7.5</td>
<td>INTEGER-GT</td><td>INTGT</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>INTEGER-LE</td><td>INTLE</td><td>Available as of V7.5</td>
<td>INTEGER-LE</td><td>INTLE</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>INTEGER-LT</td><td>INTLT</td><td>Available as of V7.5</td>
<td>INTEGER-LT</td><td>INTLT</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td colspan="3">
<td colspan="3">
Line 317: Line 379:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td>FLOAT-GE</td><td>FLTGE</td><td>Available as of V7.5</td>
<td>FLOAT-GE</td><td>FLTGE</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>FLOAT-GT</td><td>FLTGT</td><td>Available as of V7.5</td>
<td>FLOAT-GT</td><td>FLTGT</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>FLOAT-LE</td><td>FLTLE</td><td>Available as of V7.5</td>
<td>FLOAT-LE</td><td>FLTLE</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>FLOAT-LT</td><td>FLTLT</td><td>Available as of V7.5</td>
<td>FLOAT-LT</td><td>FLTLT</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
</tr>
</tr>
<tr>
<tr>
<td colspan="3">
<td colspan="3">
Line 337: Line 405:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td>DATETIME-GE</td><td>DTGE</td><td>Available as of V7.5</td>
<td>DATETIME-GE</td><td>DTGE</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>DATETIME-GT</td><td>DTGT</td><td>Available as of V7.5</td>
<td>DATETIME-GT</td><td>DTGT</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>DATETIME-LE</td><td>DTLE</td><td>Available as of V7.5</td>
<td>DATETIME-LE</td><td>DTLE</td><td>Available as of V7.5</td>
</tr>
</tr>
<tr>
<tr>
<td>DATETIME-LT</td><td>DTLT</td><td>Available as of V7.5</td>
<td>DATETIME-LT</td><td>DTLT</td><td>Available as of V7.5</td>
</tr>
</tr>
</table>
</table>
 
==== Concatenated fields ====
==== Concatenated fields ====
<table>
<table>
Line 359: Line 431:
<th>Notes</th>
<th>Notes</th>
</tr>
</tr>
<tr>
<tr>
<td>CONCATENATION-OF</td>
<td>CONCATENATION-OF</td>
Line 365: Line 438:
</tr>
</tr>
</table>
</table>
 
 
==== Automatic fields ====
==== Automatic fields ====
<table>
<table>
Line 375: Line 448:
<th>Notes</th>
<th>Notes</th>
</tr>
</tr>
<tr>
<tr>
<td>
<td>
Line 388: Line 462:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td colspan="3">
<td colspan="3">
Line 393: Line 468:
</td>
</td>
</tr>
</tr>
<tr>
<tr>
<td>CREATE-TIME</td><td>CRTM</td><td>Not allowed for fields defined as REPEATABLE</td>
<td>CREATE-TIME</td><td>CRTM</td><td>Not allowed for fields defined as REPEATABLE</td>
</tr>
</tr>
<tr>
<tr>
<td>CREATE-TIMEUTC</td><td>CRTMU</td><td>Not allowed for fields defined as REPEATABLE</td>
<td>CREATE-TIMEUTC</td><td>CRTMU</td><td>Not allowed for fields defined as REPEATABLE</td>
</tr>
</tr>
<tr>
<tr>
<td>UPDATE-TIME</td><td>UPTM</td><td>Not allowed for fields defined as REPEATABLE</td>
<td>UPDATE-TIME</td><td>UPTM</td><td>Not allowed for fields defined as REPEATABLE</td>
</tr>
</tr>
<tr>
<tr>
<td>UPDATE-TIMEUTC</td><td>UPTMU</td><td>Not allowed for fields defined as REPEATABLE</td>
<td>UPDATE-TIMEUTC</td><td>UPTMU</td><td>Not allowed for fields defined as REPEATABLE</td>
</tr>
</tr>
<tr>
<tr>
<td>CREATE-USER</td><td>CRUS</td><td>Not allowed for fields defined as REPEATABLE</td>
<td>CREATE-USER</td><td>CRUS</td><td>Not allowed for fields defined as REPEATABLE</td>
</tr>
</tr>
<tr>
<tr>
<td>UPDATE-USER</td><td>UPUS</td><td>Not allowed for fields defined as REPEATABLE</td>
<td>UPDATE-USER</td><td>UPUS</td><td>Not allowed for fields defined as REPEATABLE</td>
</tr>
</tr>
</table>
</table>
 
==== Defining a field inside a field group ====
==== Defining a field inside a field group ====
<table>
<table>
Line 421: Line 502:
<th>Notes</th>
<th>Notes</th>
</tr>
</tr>
<tr>
<tr>
<td>FIELDGROUP</td>
<td>FIELDGROUP</td>
Line 427: Line 509:
</tr>
</tr>
</table>
</table>
 
===OCCURS and LENGTH clauses===
===OCCURS and LENGTH clauses===
<p>
<p>
Line 434: Line 516:
All preallocated fields (fields that have an OCCURS clause) must be defined before any records are added to the file. </p>
All preallocated fields (fields that have an OCCURS clause) must be defined before any records are added to the file. </p>
<p class="note"><b>Note:</b> After records are loaded, you can add a preallocated field definition only by reinitializing the file, defining all the fields-including the new preallocated field-and reloading the records. Non-preallocated field definitions can be added at any time. </p>
<p class="note"><b>Note:</b> After records are loaded, you can add a preallocated field definition only by reinitializing the file, defining all the fields-including the new preallocated field-and reloading the records. Non-preallocated field definitions can be added at any time. </p>
 
===Defining field retrieval attributes===
===Defining field retrieval attributes===
<p>
<p>
Line 440: Line 522:
<p>
<p>
For details, see [[File statistics and tuning#Monitoring field retrievals in FIND statements|Monitoring field retrievals in FIND statements]].</p>
For details, see [[File statistics and tuning#Monitoring field retrievals in FIND statements|Monitoring field retrievals in FIND statements]].</p>
 
==Implementing the date-time stamp feature (DTS)==
==Implementing the date-time stamp feature (DTS)==
<p>The date-time stamp feature in <var class="product">Model&nbsp;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&nbsp;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>
and [[Adding a Date-Time Stamp field]] for rules on using the feature.</p>
<p>
See [[Setting up the date-time stamp field]] for the steps the System Manger must take before this feature is used.
</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><var class="product">Model&nbsp;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&nbsp;204</var> to issue the following response, when a user issues a DEFINE command:</p>
<p>
<var class="product">Model&nbsp;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&nbsp;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>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>
<p>
<p>&nbsp;</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]]

Latest revision as of 21:21, 7 April 2017

This chapter describes the use of the DEFINE FIELD command, which allows you to define the fields in a file. For the full syntax, follow that link.

Defining fields

After you CREATE and INITIALIZE a Model 204 file, use the DEFINE command or the IFDFLD Host Language Interface function to establish the names and types of the fields in the file.

Syntax

The format of the DEFINE command is:

DEFINE FIELD name [(attribute [,[attribute ...]]) | WITH [attribute][,[attribute ...]]]

where:

  • name is a 1 to 255 character name that must begin with a letter and can contain any alphanumeric characters, including spaces, except:

    ?? ?$ ?& @ (or an alternative delete character) # (or an alternative flush character) ;

  • attribute is a member of the list in Field attributes.

    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 ORDERED and NON-ORDERED attributes.

Example

In the following example, the field CUSTID is named and given the ORDERED CHARACTER attribute:

DEFINE FIELD CUSTID ORDERED CHARACTER

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.

Note: Every attribute has a default value. Therefore, you only need to specify the attribute if it is not the default.

When to use the FIELD keyword

The keyword FIELD is required before field names that begin with the word FIELD, PRINTER, or DATASET. It is optional with other field names. If FIELD is specified, only one field can be defined or redefined per command. For example:

DEFINE FIELD POLICYHOLDER DEFINE POLICYHOLDER

Each example above defines a field with the name POLICYHOLDER. The following example defines a field with the name FIELD LOCATION:

DEFINE FIELD FIELD LOCATION

Defining sort key, hash key, and record security fields

The DEFINE command cannot be used to define sort key fields, hash key fields, or record security fields. These fields can be defined only with the INITIALIZE command and the appropriate parameter settings.

Field attributes

The attributes listed in the following tables are introduced in 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 the ORDERED attribute) that can be specified with the DEFINE FIELD command, which are also described in Field design.

Indexing attributes

The overall effect of the defaults is that, unless specified, the field is not indexed.

Indexing field attributes with the DEFINE command
AttributeAbbreviationDefault
ORDERED CHARACTER

NON-ORDERED

ORD CHAR

NORD

NON-ORDERED
ORDERED NUMERIC

NON-ORDERED

ORD NUM

NORD

NON-ORDERED
KEY

NON-KEY

 

NKEY

NON-KEY
FRV

NON-FRV

The ORD attribute is preferable; shown for compatibility.

 

NFRV

NON-FRV
[NUMERIC] RANGE

NON-RANGE

Obsolete; supported for compatibility.

NR

NNR

NON-RANGE

Data types

In most cases, only one of these may be specified on any field (see the UTF attributes). The default is STRING

Data type attributes with the DEFINE command
Attribute Abbreviation Notes
STRING STR
BINARY BIN
BINARY-LARGE-OBJECT

CHARACTER-LARGE-OBJECT

BLOB

CLOB

Must have Table E enabled

FLOAT FLT Must have LEN specified
DATETIME DT
UTF-8

UTF-16

UTF8

UTF16

Must be used in conjunction with the BLOB or CLOB attribute

VISIBLE

INVISIBLE

VIS

INV

Data content attributes

Data content field attributes with the DEFINE command
Attribute Abbreviation Default

LENGTH m

LEN m

No preallocated length

OCCURS n OCC n No preallocated occurrences

PAD character

 

character = X'00'

DEFERRABLE

NON-DEFERRABLE

DEF

NDEF

DEFERRABLE
UPDATE IN PLACE

UPDATE AT END

UP

UE

UPDATE IN PLACE
DEFAULT-VALUE

STORE-DEFAULT

STORE-NULL

DV

SD

SN

 

LITERAL

LITERAL

AT-MOST-ONE

EXACTLY-ONE

REPEATABLE

ONE

EXONE

REPT

REPT (except in 1NF files), or inside a field group (where it is EXONE)

CODED

NON-CODED

COD

NCOD

NON-CODED
FEW-VALUED

MANY-VALUED

FV

MV

MANY-VALUED

Field constraints

More than one constraint may be set on a field. For example, if you only want to accept integer values between 5 and 99, then you can code:

DEFINE FIELD fieldname WITH INTGE 5 INTLE 99

Field constraint attributes with DEFINE command
Attribute Abbreviation Notes
UNIQUE

NON-UNIQUE

UNIQ

NUNIQ

NON-UNIQUE is default

LEVEL

LEV

See Model 204 security features

Field length constraints

LENGTH-EQLEQAvailable as of V7.5
LENGTH-GELGEAvailable as of V7.5
LENGTH-LELLEAvailable as of V7.5
Integer value constraints

(validate contents against permissible integer value)

INTEGER-GEINTGEAvailable as of V7.5
INTEGER-GTINTGTAvailable as of V7.5
INTEGER-LEINTLEAvailable as of V7.5
INTEGER-LTINTLTAvailable as of V7.5
Float value constraints

(validate contents against permissible float value)

FLOAT-GEFLTGEAvailable as of V7.5
FLOAT-GTFLTGTAvailable as of V7.5
FLOAT-LEFLTLEAvailable as of V7.5
FLOAT-LTFLTLTAvailable as of V7.5
Date Time value constraints

(validate contents against permissible date times value)

DATETIME-GEDTGEAvailable as of V7.5
DATETIME-GTDTGTAvailable as of V7.5
DATETIME-LEDTLEAvailable as of V7.5
DATETIME-LTDTLTAvailable as of V7.5

Concatenated fields

Concatenated field attributes with the DEFINE command
Attribute Abbreviation Notes
CONCATENATION-OF CAT All source fields must be EXACTLY-ONE


Automatic fields

Automatic field attributes with the DEFINE command
Attribute Abbreviation Notes

COUNT-OCCURRENCES-OF

CTO

Followed by what it is you are counting;
not allowed for fields defined as REPEATABLE

Tracking updates with automatic fields
CREATE-TIMECRTMNot allowed for fields defined as REPEATABLE
CREATE-TIMEUTCCRTMUNot allowed for fields defined as REPEATABLE
UPDATE-TIMEUPTMNot allowed for fields defined as REPEATABLE
UPDATE-TIMEUTCUPTMUNot allowed for fields defined as REPEATABLE
CREATE-USERCRUSNot allowed for fields defined as REPEATABLE
UPDATE-USERUPUSNot allowed for fields defined as REPEATABLE

Defining a field inside a field group

Linking a field to a field group with the DEFINE command
Attribute Abbreviation Notes
FIELDGROUP FG If not the last attribute specified, requires ' AND ' after it

OCCURS and LENGTH clauses

The variables n and m specified for OCCURS and LENGTH must be decimal numbers between 1 and 255. The PAD character can be specified in decimal, hexadecimal (X'xx'), or character (C'c') form, and can take on any value equivalent to a number between 0 and 255.

All preallocated fields (fields that have an OCCURS clause) must be defined before any records are added to the file.

Note: After records are loaded, you can add a preallocated field definition only by reinitializing the file, defining all the fields-including the new preallocated field-and reloading the records. Non-preallocated field definitions can be added at any time.

Defining field retrieval attributes

If you do not know if a field will be used in retrievals, you can define it initially as NON-KEY, NON-ORDERED, and NON-RANGE. Then, you will be able to monitor the use of the field in FIND statements using information written to the journal data set and redefine it as KEY, NUMERIC RANGE, or ORDERED when necessary.

For details, see Monitoring field retrievals in FIND statements.

Implementing the date-time stamp feature (DTS)

The date-time stamp feature in Model 204 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.

See Setting up the date-time stamp field for the steps the System Manger must take before this feature is used.

See Adding a date-time stamp field for rules about using the date-time stamp feature.

Preventing definition of new field names

Model 204 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 Model 204 to issue the following response, when a user issues a DEFINE command:

*** M204.1261: NEW FIELD NAMES NOT PERMITTED

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 FOPT parameter discussion for more detail.