Field attribute combinations: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (Admin moved page Field Attribute Combinations to Field attribute combinations without leaving a redirect: caps)
(Automatically generated page update)
 
(One intermediate revision by one other user not shown)
Line 2: Line 2:
<p>When deciding on combinations of field attributes, use the following chart to see if the combination you want to use is valid. <br />
<p>When deciding on combinations of field attributes, use the following chart to see if the combination you want to use is valid. <br />
The [[#Key to chart codes|chart key]] explains the codes used in the chart. </p>
The [[#Key to chart codes|chart key]] explains the codes used in the chart. </p>
<table>
<p class="caption">Field attribute combinations</p>
<caption>Field attribute combinations</caption>
<table style="font-size:80%">
<tr class="head">
<tr class="head">
<th>Attribute</th>
<th>Attribute</th>
Line 32: Line 32:
<th>UTF16</th>
<th>UTF16</th>
</tr>
</tr>
<tr>
<tr>
<td>KEY</td>
<td>KEY</td>
Line 60: Line 61:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>ORD CHAR </td>
<td>ORD CHAR </td>
Line 88: Line 90:
<td>N</td>
<td>N</td>
</tr>
</tr>
<tr>
<tr>
<td>ORD NUM </td>
<td>ORD NUM </td>
Line 116: Line 119:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>FRV</td>
<td>FRV</td>
Line 144: Line 148:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>UNIQUE (UNQ)</td>
<td>UNIQUE (UNQ)</td>
Line 172: Line 177:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>NUM RANGE (NR)</td>
<td>NUM RANGE (NR)</td>
Line 200: Line 206:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>DEFERRABLE (DEF)</td>
<td>DEFERRABLE (DEF)</td>
Line 228: Line 235:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>(LVL)</td>
<td>(LVL)</td>
Line 256: Line 264:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>AT-MOST-ONE (ONE)</td>
<td>AT-MOST-ONE (ONE)</td>
Line 284: Line 293:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>INVISIBLE (INV)</td>
<td>INVISIBLE (INV)</td>
Line 312: Line 322:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>STRING (STR)</td>
<td>STRING (STR)</td>
Line 340: Line 351:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>FLOAT (FLT)</td>
<td>FLOAT (FLT)</td>
Line 368: Line 380:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>BINARY (BIN)</td>
<td>BINARY (BIN)</td>
Line 396: Line 409:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>CODED (COD)</td>
<td>CODED (COD)</td>
Line 424: Line 438:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>FEW VALUED (FV)</td>
<td>FEW VALUED (FV)</td>
Line 452: Line 467:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>OCCURS (OCC)</td>
<td>OCCURS (OCC)</td>
Line 480: Line 496:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>LENGTH (LEN)</td>
<td>LENGTH (LEN)</td>
Line 508: Line 525:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>PAD</td>
<td>PAD</td>
Line 536: Line 554:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>UPDATE (UPD)</td>
<td>UPDATE (UPD)</td>
Line 564: Line 583:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>BINARY_LARGE_OBJECT (BLOB)</td>
<td>BINARY_LARGE_OBJECT (BLOB)</td>
Line 592: Line 612:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>CHARACTER_LARGE_OBJECT (CLOB)</td>
<td>CHARACTER_LARGE_OBJECT (CLOB)</td>
Line 620: Line 641:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>MINLOBE (MINLOBE)</td>
<td>MINLOBE (MINLOBE)</td>
Line 648: Line 670:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>CHUNK (CHUNK)</td>
<td>CHUNK (CHUNK)</td>
Line 676: Line 699:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>UTF8 (UTF-8)</td>
<td>UTF8 (UTF-8)</td>
Line 704: Line 728:
<td>&nbsp;</td>
<td>&nbsp;</td>
</tr>
</tr>
<tr>
<tr>
<td>UTF16 (UTF-16)</td>
<td>UTF16 (UTF-16)</td>
Line 733: Line 758:
</tr>
</tr>
</table>
</table>
====Key to chart codes====
====Key to chart codes====
<table>
<table>
Line 739: Line 765:
<th>Meaning</th>
<th>Meaning</th>
</tr>
</tr>
<tr>
<tr>
<td>N </td>
<td>N </td>
<td>This attribute combination is not valid.</td>
<td>This attribute combination is not valid.</td>
</tr>
</tr>
<tr>
<tr>
<td>R </td>
<td>R </td>
Line 751: Line 779:
<td>One of these attributes is required. You can choose any one of the attributes marked, but you must choose at least one.</td>
<td>One of these attributes is required. You can choose any one of the attributes marked, but you must choose at least one.</td>
</tr>
</tr>
<tr>
<tr>
<td>=1</td>
<td>=1</td>
<td>The OCCURS clause is valid with this attribute only if defined as OCCURS=1. You cannot enter multiple field values for fields with these attributes.</td>
<td>The OCCURS clause is valid with this attribute only if defined as OCCURS=1. You cannot enter multiple field values for fields with these attributes.</td>
</tr>
</tr>
<tr>
<tr>
<td>F </td>
<td>F </td>
Line 760: Line 790:
</tr>
</tr>
</table>
</table>
<p>Some of the invalid combinations are direct conflicts, such as UNIQUE and DEFERRABLE; others describe meaningless situations or unusable fields, such as ORDERED CHARACTER and ORDERED NUMERIC. </p>
<p>
<p>In addition, some attributes <var class="term">require</var> other attributes. FLOAT, for example, requires a LENGTH specification. </p>
Some of the invalid combinations are direct conflicts, such as UNIQUE and DEFERRABLE; others describe meaningless situations or unusable fields, such as ORDERED CHARACTER and ORDERED NUMERIC. </p>
<p>Field descriptions that contain invalid combinations are rejected. </p>
<p>
<p>The <b>Field attribute combinations</b> chart is for Entry Order files. More stringent restrictions are placed on fields that are used as sort keys, hash keys, or record security fields. These restrictions are summarized in the discussion in the <var class="book">Rocket Model 204 Parameter and Command Reference</var>.</p>
In addition, some attributes <var class="term">require</var> other attributes. FLOAT, for example, requires a LENGTH specification. </p>
<p>
Field descriptions that contain invalid combinations are rejected. </p>
<p>
The "Field attribute combinations" chart is for Entry Order files. More stringent restrictions are placed on fields that are used as sort keys, hash keys, or record security fields. These restrictions are summarized in the discussion in [[DEFINE FIELD command]].</p>


<p>&nbsp;</p>
[[Category:Model 204 files]]
[[Category:File management]]

Latest revision as of 22:45, 9 May 2014

Combining attributes

When deciding on combinations of field attributes, use the following chart to see if the combination you want to use is valid.
The chart key explains the codes used in the chart.

Field attribute combinations

Attribute KEY ORD CHAR ORD NUM FRV UNQ NR DEF LVL ONE INV STR FLT BIN COD FV OCC LEN PAD UPD BLOB CLOB MINLOBE CHUNK UTF8 UTF16
KEY                                       N N        
ORD CHAR     N N               N                       N N
ORD NUM   N   N   N                           N N        
FRV R N N   N                             N N        
UNIQUE (UNQ)   @ @ N     N                         N N        
NUM RANGE (NR)     N                 N       =1       N N        
DEFERRABLE (DEF) @ @ @   N @                           N N        
(LVL)                                                  
AT-MOST-ONE (ONE)                   N                              
INVISIBLE (INV) @ @ @     @     N     N       N N N N N N        
STRING (STR)                       N N             N N        
FLOAT (FLT)   N       N       N N   N F     R N   N N        
BINARY (BIN)                     N N         N N   N N        
CODED (COD)                       F         F N   N N        
FEW VALUED (FV)         @                 @           N N        
OCCURS (OCC)           =1     =1 N     @ @     @                
LENGTH (LEN)                   N   @ N F   @       N N        
PAD                   N   N N N     R     N N        
UPDATE (UPD)                   N                              
BINARY_LARGE_OBJECT (BLOB) N N N N N N N     N N N N N N   N N     N        
CHARACTER_LARGE_OBJECT (CLOB) N N N N N N N     N N N N N N   N N   N          
MINLOBE (MINLOBE) N N N N N N N     N N N N N N   N N   N          
CHUNK (CHUNK) N N N N N N N     N N N N N N   N N   N          
UTF8 (UTF-8) N N N N N N N     N N N N N N   N N   N          
UTF16 (UTF-16) N N N N N N N     N N N N N N   N N   N          

Key to chart codes

Code Meaning
N This attribute combination is not valid.
R This attribute combination is required.
@ One of these attributes is required. You can choose any one of the attributes marked, but you must choose at least one.
=1 The OCCURS clause is valid with this attribute only if defined as OCCURS=1. You cannot enter multiple field values for fields with these attributes.
F The FLOAT attribute requires the LEN attribute. Since the FLOAT attribute can also be used with the CODED attribute, this is the only circumstance that the LEN attribute is valid with CODED attribute.

Some of the invalid combinations are direct conflicts, such as UNIQUE and DEFERRABLE; others describe meaningless situations or unusable fields, such as ORDERED CHARACTER and ORDERED NUMERIC.

In addition, some attributes require other attributes. FLOAT, for example, requires a LENGTH specification.

Field descriptions that contain invalid combinations are rejected.

The "Field attribute combinations" chart is for Entry Order files. More stringent restrictions are placed on fields that are used as sort keys, hash keys, or record security fields. These restrictions are summarized in the discussion in DEFINE FIELD command.

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=Field_attribute_combinations&oldid=69278"