Defining field attributes with FILEMGMT: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
(Automatically generated page update)
 
(15 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==Field Attributes==
==Field attributes==
<p>To display the Field Attributes screens, choose one of the following methods:</p>
<p>
To display the Field Attributes screens, choose one of the following methods:</p>
<ul>
<ul>
<li>Press the PF11 (ATTributes) key from the Field Name List screen.</li>
<li>Press the F11 (ATTributes) key from the [[Defining fields with FILEMGMT|Field Name List screen]].</li>
<li>Select a Define or Redefine function from the primary screen and specify a particular field name. For Rename and Delete you must first use the Field Name List screen.</li>
 
<li>Select the Define or Redefine function from the primary screen and specify a particular field name. For Rename and Delete, you must first use the Field Name List screen.</li>
</ul>
</ul>
<p>FILEMGMT displays the Field Attributes screen shown on [[#Field Attribute screen: initial defaults|Field Attribute screen: initial defaults]].</p>
<p>
<p>Proceeding to this screen stages the fields you specified on the Field Name List screen or the field you specified on the primary screen for the function you selected on the primary screen.</p>
FILEMGMT displays the Field Attributes screen shown on [[#Field Attribute screen: initial defaults|Field Attribute screen: initial defaults]].</p>
<p>You use the Field Attributes screen to specify or view values for field attributes. When the field attributes are displayed for a field for the first time, FILEMGMT shows the <var class="product">Model&nbsp;204</var> default values. For existing or staged fields, FILEMGMT shows the current values.  </p>
<p>
<p>The following field attributes cannot be redefined through FILEMGMT, because they can be redefined only if the file is reorganized:</p>
Proceeding to this screen stages either: </p>
<ul>
<ul>
<li>Datatype (STRING, BINARY, FLOAT, and so on.)</li>
<li>The fields you specified on the Field Name List screen </li>
<li>INVISIBLE</li>
<li>The field you specified on the primary screen for the function you selected on the primary screen. </li>
<li>PREALLOCATED</li>
<li>LENGTH, OCCURS (if preallocated)</li>
<li>Few-Valued/Many-Valued (unless NONCODED and being redefine from non-FRV to FRV)</li>
</ul>
</ul>
<p>FILEMGMT displays screens for each field you specified on the Field Name List screen or the Field Attribute screen; the fields are displayed in the same order as on the Field Name List screen. You can advance to the next field by pressing the PF11 (NEXtfld) key, or return to the previous field by pressing the PF10 (PREvfld) key. </p>
<p>
<p>FILEMGMT does not save any of the information you enter until you press one of the following function keys from the screen:</p>
You use the Field Attributes screen to specify or view values for field attributes. When the field attributes are displayed for a field for the first time, FILEMGMT shows the <var class="product">Model&nbsp;204</var> default values. For existing or staged fields, FILEMGMT shows the current values.  </p>
<p>
The following field attributes cannot be redefined through FILEMGMT, because they can be redefined only if the file is reorganized:</p>
<ul>
<li>Data type (<var>STRING</var>, <var>BINARY</var>, <var>FLOAT</var>, and so on.)</li>
 
<li><var>INVISIBLE</var></li>
 
<li><var>PREALLOCATED</var></li>
 
<li><var>LENGTH</var>, <var>OCCURS</var> (if preallocated)</li>
 
<li><var>FEW-VALUED</var>/<var>MANY-VALUED</var> (unless <var>NONCODED</var> and being redefined from non-<var>FRV</var> to <var>FRV</var>)</li>
</ul>
<p>
FILEMGMT displays screens for each field you specified on the Field Name List screen or the Field Attribute screen. The fields are displayed in the same order as on the Field Name List screen. You can advance to the next field by pressing the F11 (NEXtfld) key, or return to the previous field by pressing the F10 (PREvfld) key. </p>
<p>
FILEMGMT does not save any of the information you enter until you press one of the following function keys from the screen:</p>
<table>
<table>
<tr>
<tr>
<td>PF4</td>
<td>F4</td>
<td>RECords</td>
<td>RECords</td>
</tr>
</tr>
<tr>
<tr>
<td>PF6</td>
<td>F6</td>
<td>COMmands</td>
<td>COMmands</td>
</tr>
</tr>
<tr>
<tr>
<td>PF10</td>
<td>F10</td>
<td>PREvfld</td>
<td>PREvfld</td>
</tr>
</tr>
<tr>
<tr>
<td>PF11</td>
<td>F11</td>
<td>NEXtfld</td>
<td>NEXtfld</td>
</tr>
</tr>
<tr>
<tr>
<td>PF12</td>
<td>F12</td>
<td>END </td>
<td>END </td>
</tr>
</tr>
</table>
</table>
<p>Only these PF keys verify data on the screen (PF7 and PF8 do not).</p>
<p>
<p>If you are deleting or renaming a field, the items on the Field Attributes screens are entry-protected and cannot be changed. </p>
Only these PF keys verify data on the screen (F7 and F8 do not).</p>
====Field Attribute screen: initial defaults====
<p>
<p>The following screen shows the default values for FILEMGMT field attributes. This screen is displayed when you define a new field.</p>
If you are deleting or renaming a field, the items on the Field Attributes screens are entry-protected and cannot be changed. </p>
<p>To change an attribute, you can either type over a highlighted value or position the cursor on a value cycling field and use PF7 and PF8 to display new values. When you change a value, the screen can change to reflect a variety of logical dependencies. New attributes appear, and incompatible attributes are hidden. For example, if you change the default value REPEATABLE to AT-MOST-ONE, the minimum and maximum occurs input fields disappear (see [[#Field Attribute Screen: Example 1 (NONORDERED, PREALLOCATED)|Field Attribute Screen: Example 1 (NONORDERED, PREALLOCATED)]]).</p>
 
<p>The attributes related to ORDERED fields appear on the same screen as other attributes, and the Access/Target Descriptors (formerly called: physical format) are on a separate part of the screen.   </p>
===Field Attribute screen: initial defaults===
<p>
The following screen shows the default values for FILEMGMT field attributes. This screen is displayed when you define a new field.</p>
<p>
To change an attribute, you can either type over a highlighted value or position the cursor on a value cycling field and use F7 and F8 to display new values. When you change a value, the screen can change to reflect a variety of logical dependencies. New attributes appear, and incompatible attributes are hidden. For example, if you change the default value <var>REPEATABLE</var> to <var>AT-MOST-ONE</var>, the minimum and maximum Occurs input fields disappear (see [[#Field Attribute Screen: Example 1 (NONORDERED, PREALLOCATED)|Field Attribute Screen: Example 1 (NONORDERED, PREALLOCATED)]]).</p>
<p>
The attributes related to <var>ORDERED</var> fields appear on the same screen as other attributes, and the Access/Target Descriptors (formerly called: physical format) are on a separate part of the screen. </p>
<table>
<table>
<tr>
<tr><td>
<td>
<p class="code">FILEMGMT                        Field Attributes
<p class="code">
FILEMGMT                        Field Attributes


FILENAME: VEHICLES
FILENAME: VEHICLES
Line 56: Line 80:


Data Type NON-PREALLOCATED  Average Length                        Security
Data Type NON-PREALLOCATED  Average Length                        Security
STRING      REPEATABLE     IN BYTES 20__                        LVL: 0__
STRING      REPEATABLE     in Bytes 20__                        LVL: 0__


UPD IN PLACE                           MIN. OCCURS 1__      NO. OF UNIQUE
UPD IN PLACE                         MIN. OCCURS 1__      NO. OF UNIQUE
                                      MAX. OCCURS 1__      VALUES: ________
                                      MAX. OCCURS 1__      VALUES: ________
NON-KEY      NON-ORDERED
NON-KEY      NON-ORDERED
                                      ===== ACCESS/TARGET Descriptors =====
              NON-NUMERIC-RANGE        Picture      Format  FIXED
                                      X(20)_______  NO MIXED CASE


                                      <b></b>===== ACCESS/TARGET Descriptors <b></b>=====
              NON-NUMERIC-RANGE      Picture      Format  FIXED
                                      X(20)_______  NO MIXED CASE




Line 73: Line 96:
1=HELp        2=            3=QUIt    4=RECords    5=COPy      6=COMmands
1=HELp        2=            3=QUIt    4=RECords    5=COPy      6=COMmands
7=PREv value  8=NEXt value  9=SIZe  10=PRVfield  11=NXTfield  12=END
7=PREv value  8=NEXt value  9=SIZe  10=PRVfield  11=NXTfield  12=END
</p></td>
</p></td>
</tr>
</tr>
</table>
</table>
<p>The date/time stamp field:</p>
<p>
The date-time stamp field:</p>
<ul>
<ul>
<li>Must be STRING. Rocket Software recommends ORDERED CHARACTER</li>
<li>Must be <var>STRING</var>; and Rocket Software recommends the <var>ORDERED CHARACTER</var> attribute.</li>
<li>Cannot be defined as INVISIBLE</li>
<li>Cannot be defined as <var>INVISIBLE</var>.</li>
<li>Cannot be a multiple occurring field </li>
<li>Cannot be a multiply occurring field. </li>
<li>Can be pre-allocated</li>
<li>Can be preallocated.</li>
</ul>
</ul>
====Field Attribute Screen: Example 1 (NONORDERED, PREALLOCATED)====
 
<p>The following example shows what happens when you change the attributes to NONORDERED, PREALLOCATED, and KEY.</p>
===Field Attribute Screen: Example 1 (NONORDERED, PREALLOCATED)===
<p>Notice that "average length" becomes "fixed length"; the Pad Char input field appears; an occurrence count input field follows REPEATABLE; and the MIN. OCCURS and MAX. OCCURS input fields are hidden. These are examples of dynamic screen management, described more fully in [[#Field attribute dependency rules|Field attribute dependency rules]].</p>
<p>
The following example shows what happens when you change the attributes to <var>NONORDERED</var>, <var>PREALLOCATED</var>, and <var>KEY</var>.</p>
<p>
Notice that <b>Average Length</b> becomes <b>Fixed length</b>; the <b>Pad Char</b> input field appears; an occurrence count input field follows <b>REPEATABLE</b>; and the <b>MIN. OCCURS</b> and <b>MAX. OCCURS</b> input fields are hidden. These are examples of dynamic screen management, described more fully in [[#Field attribute dependency rules|Field attribute dependency rules]].</p>
 
<table>
<table>
<tr>
<tr>
Line 96: Line 123:


Data Type  PREALLOCATED      Fixed Length                        Security
Data Type  PREALLOCATED      Fixed Length                        Security
STRING        REPEATABLE 1__  IN BYTES ____                      LVL:  0__
STRING        REPEATABLE 1__  in Bytes ____                      LVL:  0__


UPD IN PLACE                                                NO. OF UNIQUE
UPD IN PLACE                                                NO. OF UNIQUE
Line 102: Line 129:
KEY        NON-ORDERED
KEY        NON-ORDERED
                               ===== ACCESS/TARGET Descriptors =====
                               ===== ACCESS/TARGET Descriptors =====
FRV        NON-NUMERIC-RANGE  Picture         Format FIXED
FRV        NON-NUMERIC-RANGE  Picture       Format FIXED
MANY VALUED                     X(20)_______   NO MIXED CASE
MANY VALUED                   X(20)_______   NO MIXED CASE
 




Line 115: Line 141:
</tr>
</tr>
</table>
</table>
====Field Attribute Screen: Example 2 (ORDERED)====
 
<p>When you specify an ORDERED field, a new set of parameters appears at the bottom of the screen. </p>
===Field Attribute Screen: Example 2 (ORDERED)===
<p>Notice that the NON-UNIQUE attribute appears, while the FRV attribute has been hidden. </p>
<p>
When you specify an <var>ORDERED</var> field, a new set of parameters appears at the bottom of the screen. </p>
<p>
Notice that the <var>NON-UNIQUE</var> attribute appears, while the <var>FRV</var> attribute has been hidden. </p>
 
<table>
<table>
<tr>
<tr><td>
<td>
<p class="code">FILEMGMT                        Field Attributes
<p class="code">FILEMGMT                        Field Attributes


Line 126: Line 155:
FIELDNAME: ABCFIELD
FIELDNAME: ABCFIELD
Data Type  NON-PREALLOCATED  Average Length                      Security
Data Type  NON-PREALLOCATED  Average Length                      Security
STRING        REPEATABLE      IN BYTES ____                      LVL:  0__
STRING        REPEATABLE      in Bytes ____                      LVL:  0__


UPD IN PLACE                        MIN. OCCURS 1__        NO. OF UNIQUE
UPD IN PLACE                        MIN. OCCURS 1__        NO. OF UNIQUE
Line 132: Line 161:
NON-KEY    ORDERED CHAR NON-UNIQUE
NON-KEY    ORDERED CHAR NON-UNIQUE
                                     ==== ACCESS/TARGET Descriptors =====
                                     ==== ACCESS/TARGET Descriptors =====
           NON-NUMERIC-RANGE        Picture           Format FIXED
           NON-NUMERIC-RANGE        Picture     Format FIXED
                                     X(20)_______       NO MIXED CASE
                                     X(20)_______ NO MIXED CASE
 
<b></b>==================== Parameters for Ordered Index=====================
<b></b>==================== Parameters for Ordered Index=====================
   IMMED: 1        LRESERVE: 15% SIZING PARAMETER: THE PERCENTAGE OF
   IMMED: 1        LRESERVE: 15% SIZING PARAMETER: THE PERCENTAGE OF
(PTRS TO TABLE-B  NRESERVE: 15% THE VALUES TO BE DDED DIRECTLY, NOT
(PTRS TO TABLE-B  NRESERVE: 15% THE VALUES TO BE DDED DIRECTLY, NOT
  IN LEAF ENTRY)  SPLITPCT: 50%    BY DEFERRED UPDATE)    50%
  IN LEAF ENTRY)  SPLITPCT: 50%    BY DEFERRED UPDATE)    50%
<b></b>===>
<b></b>===>


Line 145: Line 176:
</tr>
</tr>
</table>
</table>
====Field Attribute Screen Input====
 
<p>Based on the command and your entry point, you have the following options for changing information on the screen:</p>
===Field Attribute screen input===
<p>
Based on the command and your entry point, you have the following options for changing information on the screen:</p>
<ul>
<ul>
<li>DEFINE/REDEFINE
<li>DEFINE/REDEFINE
<p>You can change the field name if you entered the Field Attributes screen from the primary screen to define a field. Otherwise, you cannot change the field name.</p>
<p>
<p>You can type over the values of any of the attributes if the field is staged for DEFINE. Some attributes are entry-protected if the field is staged for REDEFINE.</p>
You can change the field name if you entered the Field Attributes screen from the primary screen to define a field. Otherwise, you cannot change the field name.</p>
</li>
<p>
You can type over the values of any of the attributes if the field is staged for <var>DEFINE</var>. Some attributes are entry-protected if the field is staged for <var>REDEFINE</var>.</p></li>
</ul>
</ul>
<b>Note</b>
<p class="note"><b>Note:</b>
<p>Requesting a field REDEFINE that changes the average length of a non-preallocated field might generate a record REDEFINE command for each record that the field cross-references. Each record's average length is readjusted to reflect the difference between the old and new average length multiplied by the field percent rate for the record.</p>
Requesting a field <var>REDEFINE</var> that changes the average length of a non-preallocated field might generate a record <var>REDEFINE</var> command for each record that the field cross-references. Each record's average length is readjusted to reflect the difference between the old and new average length multiplied by the field percent rate for the record.</p>
<ul>
<ul>
<li>DELETE/RENAME
<li>DELETE/RENAME
<p>You can view but not change any information on this screen.</p>
<p>
</li>
You can view but not change any information on this screen.</p></li>
</ul>
</ul>
====Field Attribute screen commands====
 
<p>To issue a command, press a PF key or type a command name at the prompt (===>) and press Enter.</p>
===Field Attribute screen commands===
<p>
To issue a command, press a PF key or type a command name at the prompt (<b>===></b>), and press Enter.</p>
 
<table>
<table>
<tr class="head">
<tr class="head">
Line 168: Line 205:
<th>Meaning</th>
<th>Meaning</th>
</tr>
</tr>
<tr>
<tr>
<td>PF1 </td>
<td>F1 </td>
<td>HELP </td>
<td>HELP </td>
<td>Displays HELp text for the Field Attributes screen. </td>
<td>Displays HELp text for the Field Attributes screen. </td>
</tr>
</tr>
<tr>
<tr>
<td>PF3 </td>
<td>F3 </td>
<td>QUIt </td>
<td>QUIt </td>
<td>Exits from the Field Attributes screen and returns to the previous screen without making any changes to the current field. </td>
<td>Exits from the Field Attributes screen and returns to the previous screen without making any changes to the current field. </td>
</tr>
</tr>
<tr>
<tr>
<td>PF4 </td>
<td>F4 </td>
<td>RECords </td>
<td>RECords </td>
<td>Proceeds to the Record Name List screen. This screen lists the records in the file. Changes to the current field are saved in the dictionary.   </td>
<td>Proceeds to the [[Adding record definitions with FILEMGMT|Record Name List screen]]. This screen lists the records in the file. Changes to the current field are saved in the dictionary. </td>
</tr>
</tr>
<tr>
<tr>
<td>PF5</td>
<td>F5</td>
<td>COPY</td>
<td>COPY</td>
<td>
<td>This PF key allows you to copy attribute values from an existing field to a field being defined or redefined. To execute the <var>COPY</var> command, enter the qualified or unqualified name of the source field on the command line and press F2. All parameter values are then copied to the field being defined. This option is valid only for defining a field.
<p>This PF key allows you to copy attribute values from an existing field to a field being defined or redefined. To execute the COPY command, enter the qualified or unqualified name of the source field on the command line and press PF2. All parameter values are then copied to the field being defined. This option is valid only for defining a field.</p>
<p>
<p>If you specify the fully qualified field name, you can then copy attributes from fields in external files, provided that the external files are defined in the <var class="product">Model&nbsp;204</var> dictionary.</p>
If you specify the fully-qualified field name, you can then copy attributes from fields in external files, provided that the external files are defined in the <var class="product">Model&nbsp;204</var> dictionary.</p>
</td>
</td></tr>
</tr>
 
<tr>
<tr>
<td>PF6 </td>
<td>F6 </td>
<td>COMmands </td>
<td>COMmands </td>
<td>Proceeds to the Execute Commands screen. This screen displays the staged commands that were generated for the file and allows you to select the commands you want to execute. Changes to the current field are saved in the dictionary. </td>
<td>Proceeds to the [[Executing and deleting commands with FILEMGMT#Execute Commands screen|Execute Commands screen]]. This screen displays the staged commands that were generated for the file and allows you to select the commands you want to execute. Changes to the current field are saved in the dictionary. </td>
</tr>
</tr>
<tr>
<tr>
<td>PF7</td>
<td>F7</td>
<td>NEXt value</td>
<td>NEXt value</td>
<td>Scrolls forward through the valid values of a particular cycling input field. When there are logical conflicts between attributes, cycling values can cause other attribute input fields to be hidden or revealed.</td>
<td>Scrolls forward through the valid values of a particular cycling input field. When there are logical conflicts between attributes, cycling values can cause other attribute input fields to be hidden or revealed.</td>
</tr>
</tr>
<tr>
<tr>
<td>PF8</td>
<td>F8</td>
<td>PREv value</td>
<td>PREv value</td>
<td>Scrolls backward through the values of a cycling input field. </td>
<td>Scrolls backward through the values of a cycling input field. </td>
</tr>
</tr>
<tr>
<tr>
<td>PF9 </td>
<td>F9 </td>
<td>SIZe </td>
<td>SIZe </td>
<td>Proceeds to the File Size Definition screen. This screen displays information about the size of the file. Changes to the current field are saved in the dictionary. </td>
<td>Proceeds to the [[Managing file and table size with FILEMGMT|File Size Definition screen]]. This screen displays information about the size of the file. Changes to the current field are saved in the dictionary. </td>
</tr>
</tr>
<tr>
<tr>
<td>PF10 </td>
<td>F10 </td>
<td>PREvfld </td>
<td>PREvfld </td>
<td>Displays the previous field, defined by the order in which fields were selected on the Field Name List screen. Changes to the current field are saved in the dictionary. </td>
<td>Displays the previous field, defined by the order in which fields were selected on the Field Name List screen. Changes to the current field are saved in the dictionary. </td>
</tr>
</tr>
<tr>
<tr>
<td>PF11 </td>
<td>F11 </td>
<td>NEXtfld </td>
<td>NEXtfld </td>
<td>Displays the next field, defined by the order in which fields were selected on the Field Name List screen. Changes to the current field are saved in the dictionary.</td>
<td>Displays the next field, defined by the order in which fields were selected on the Field Name List screen. Changes to the current field are saved in the dictionary.</td>
</tr>
</tr>
<tr>
<tr>
<td>PF12 </td>
<td>F12 </td>
<td>END </td>
<td>END </td>
<td>Exits from the Field Attributes screen and returns to your entry point (Field Name List screen or primary screen). Changes to the current field are saved in the dictionary.</td>
<td>Exits from the Field Attributes screen and returns to your entry point (Field Name List screen or primary screen). Changes to the current field are saved in the dictionary.</td></tr>
</tr>
</table>
</table>
====Abbreviations====
 
<p>Another time-saving device is an extensive set of abbreviations for field attribute values. For example, you can type NP, NPRE, or NON when specifying the NON-PREALLOCATED attribute.</p>
===Abbreviations===
<b>Note</b>
<p>
<p>Some abbreviations (such as NON) are valid for several different attributes. When using such abbreviations, take careful note of which field attribute on the screen you are changing.</p>
Another time-saving device is an extensive set of abbreviations for field attribute values. For example, you can type <code>NP</code>, <code>NPRE</code>, or <code>NON</code> when specifying the <var>NON-PREALLOCATED</var> attribute.</p>
<p>[[#Abbreviations|Abbreviations]] lists value cycling input fields and their abbreviations on the Field Attribute screen.</p>
<p class="note"><b>Note:</b>
Some abbreviations (such as <var>NON</var>) are valid for several different attributes. When using such abbreviations, take careful note of which field attribute on the screen you are changing.</p>
<p>
The following table lists value-cycling input fields and their abbreviations on the Field Attribute screen:</p>
 
<table>
<table>
<caption>Value cycling input fields and abbreviations</caption>
<caption>Value-cycling input fields and abbreviations</caption>
<tr class="head">
<tr class="head">
<th>Cycled values</th>
<th>Cycled values</th>
<th>Valid abbreviations</th>
<th>Valid abbreviations</th>
</tr>
</tr>
<tr>
<tr>
<td>PREALLOCATED
<td>PREALLOCATED
NON-PREALLOCATED</td>
<br>NON-PREALLOCATED</td>
<td>P, PRE, ALLOC
<td>P, PRE, ALLOC
NP, NPRE, NON</td>
<br>NP, NPRE, NON</td>
</tr>
</tr>
<tr>
<tr>
<td>STRING
<td>STRING<br>CODED STRING<br>BINARY<br>CODED BINARY<br>FLOAT<br>CODED FLOAT<br>PURE DBCS<br>MIXED DBCS<br>CLOB<br>BLOB</td>
CODED STRING
 
BINARY
<td>S, STR<br>CS, CSTR, CDSTR<br>B, BIN<br>CB, CBIN, CDBIN<br>F, FLT<br>CF, CFL, CDFL<br>K, KANJI, DBCS<br>M, MIXED, MIX<br>CL, CLOB, CHARLOB<br>BL, BLOB, BINLOB</td>
CODED BINARY
FLOAT
CODED FLOAT
PURE DBCS
MIXED DBCS
CLOB
BLOB</td>
<td>S, STR
CS, CSTR, CDSTR
B, BIN
CB, CBIN, CDBIN
F, FLT
CF, CFL, CDFL
K, KANJI, DBCS
M, MIXED, MIX
CL, CLOB, CHARLOB
BL, BLOB, BINLOB</td>
</tr>
</tr>
<tr>
<tr>
<td>FEW VALUED
<td>FEW VALUED<br>MANY VALUED</td>
MANY VALUED</td>
<td>F, FV, FEW<br>M, MV, MANY</td>
<td>F, FV, FEW
M, MV, MANY</td>
</tr>
</tr>
<tr>
<tr>
<td>AT-MOST-ONE
<td>AT-MOST-ONE<br>REPEATABLE</td>
REPEATABLE</td>
<td>O, AT, ONE<br>R, RP, REPT</td>
<td>O, AT, ONE
R, RP, REPT</td>
</tr>
</tr>
<tr>
<tr>
<td>INVISIBLE
<td>INVISIBLE<br>UPD IN PLACE<br>UPD AT END</td>
UPD IN PLACE
<td>I, INV, INVIS<br>UP, UIP<br>UE, UAE</td>
UPD AT END</td>
<td>I, INV, INVIS
UP, UIP
UE, UAE</td>
</tr>
</tr>
<tr>
<tr>
<td>DEFERRABLE
<td>DEFERRABLE<br>NON-DEFERRABLE</td>
NON-DEFERRABLE</td>
<td>D, DEF<br>ND, NON, NDEF</td>
<td>D, DEF
ND, NON, NDEF</td>
</tr>
</tr>
<tr>
<tr>
<td>KEY
<td>KEY<br>NON-KEY</td>
NON-KEY</td>
<td>K<br>NK, NON, NKEY</td>
<td>K
NK, NON, NKEY</td>
</tr>
</tr>
<tr>
<tr>
<td>ORDERED CHAR
<td>ORDERED CHAR<br>ORDERED NUM<br>NON-ORDERED</td>
ORDERED NUM
<td>OC, ORDC, ORD<br>ON, ORDN<br>NO, NON, NORD</td>
NON-ORDERED</td>
<td>OC, ORDC, ORD
ON, ORDN
NO, NON, NORD</td>
</tr>
</tr>
<tr>
<tr>
<td>UNIQUE
<td>UNIQUE<br>NON-UNIQUE</td>
NON-UNIQUE</td>
<td>U, UN, UNIQ<br>NU, NON, NUNIQ</td>
<td>U, UN, UNIQ
NU, NON, NUNIQ</td>
</tr>
</tr>
<tr>
<tr>
<td>NUMERIC RANGE
<td>NUMERIC RANGE<br>NON NUMERIC RANGE</td>
NON NUMERIC RANGE</td>
<td>NR, RANGE<br>NNR, NON</td>
<td>NR, RANGE
NNR, NON</td>
</tr>
</tr>
<tr>
<tr>
<td>FRV
<td>FRV<br>NON-FRV</td>
NON-FRV</td>
<td>F<br>NF, NON, NFRV</td>
<td>F
NF, NON, NFRV</td>
</tr>
</tr>
<tr>
<tr>
<td>FIXED
<td>FIXED<br>VARIABLE</td>
VARIABLE</td>
<td>F, FIX<br>V, VAR</td>
<td>F, FIX
V, VAR</td>
</tr>
</tr>
<tr>
<tr>
<td>LEADING ZEROS
<td>LEADING ZEROS<br>TRAILING ZEROS<br>LEADING AND TRAILING ZEROS<br>NO LEADING OR TRAILING ZEROS<br>MIXED CASE<br>NO MIXED CASE</td>
TRAILING ZEROS
<td>L, LZ<br>T, TZ<br>LT, LTZ<br>NLT, NLTZ<br>M, MIXED, MIX<br>NM, NOMIX, UPPER</td>
LEADING AND TRAILING ZEROS
NO LEADING OR TRAILING ZEROS
MIXED CASE
NO MIXED CASE</td>
<td>L, LZ
T, TZ
LT, LTZ
NLT, NLTZ
M, MIXED, MIX
NM, NOMIX, UPPER</td>
</tr>
</tr>
</table>
</table>
====Field attribute dependency rules====
 
<p>As the examples show, the Field Attributes screen features dynamic screen management, based on a set of dependency rules governing logical relations among attributes. The dependency rules are listed here for each attribute. For complete descriptions of file parameters, refer to the Rocket <var class="product">Model&nbsp;204</var> File Manager's Guide.</p>
===Field attribute dependency rules===
<p>
As the examples show, the Field Attributes screen features dynamic screen management, based on a set of dependency rules governing logical relations among attributes. The dependency rules are listed here for each attribute. For complete descriptions of file parameters, refer to [[List of Model 204 parameters]].</p>
<table>
<table>
<tr class="head">
<tr class="head">
Line 352: Line 366:
<th>Rules</th>
<th>Rules</th>
</tr>
</tr>
<tr>
<tr>
<td>Security Level</td>
<td>Security Level</td>
<td>Independent of all other input fields. The default value is zero, indicating that field-level security is not in effect. Maximum value is 255.</td>
<td>Independent of all other input fields. The default value is zero, indicating that field-level security is not in effect. Maximum value is 255.</td>
</tr>
</tr>
<tr>
<tr>
<td>Data Type</td>
<td>Data Type</td>
<td>
<td>Independent of all other input fields. However, this string attribute includes the values <var>CODED STRING</var>, <var>CODED BINARY</var>, and <var>CODED FLOAT</var> to enforce the association of <var>CODED</var> with one of these three data types.
<p>Independent of all other input fields. However, this string attribute includes the values CODED STRING, CODED BINARY, and CODED FLOAT to enforce the association of CODED with one of these three data types.</p>
<p>
<p>The double-byte character set (DBCS) parameters are allowed only when the system parameter DBCSENV indicates that DBCS is supported at your site.</p>
The double-byte character set (DBCS) parameters are allowed only when the system parameter <var>DBCSENV</var> indicates that DBCS is supported at your site.</p></td></tr>
</td>
 
</tr>
<tr>
<tr>
<td>Preallocated/Non</td>
<td>Preallocated/Non</td>
<td>
<td><var>PREALLOCATED</var> means that space is reserved in Table B for the field. Use the <b>REPEATABLE</b> input field to indicate the number of occurrences to preallocate. <var>PREALLOCATED</var> implies <b>Fixed Length</b> and conflicts with the attribute <var>INVISIBLE</var>.
<p>PREALLOCATED means that space is reserved in Table B for the field. Use the REPEATABLE input field to indicate the number of occurrences to preallocate. PREALLOCATED implies Fixed Length and conflicts with the attribute INVISIBLE.</p>
<p>
<p>The default setting is NON-PREALLOCATED, in which case the number of occurrences cannot be entered in the REPEATABLE input field. For Large Object (CLOB) or BLOB) fields, preallocation refers only to the pointer entry stored in Table B for a Large Object field. The pointer entry is 27 bytes for each preallocated Large Object field and 30 bytes for each non-preallocated field.</p>
The default setting is <var>NON-PREALLOCATED</var>, in which case the number of occurrences cannot be entered in the <b>REPEATABLE</b> input field. For Large Object (<var>CLOB</var>) or <var>BLOB</var>) fields, preallocation refers only to the pointer entry stored in Table B for a Large Object field. The pointer entry is 27 bytes for each preallocated Large Object field and 30 bytes for each non-preallocated field.</p></td></tr>
</td>
 
</tr>
<tr>
<tr>
<td>Length</td>
<td>Length</td>
<td>
<td>The meaning of the <b>Length</b> input field depends on data type and preallocation. <var>FLOAT</var> implies <b>Precision</b>. Otherwise, <var>NON-PREALLOCATED</var> implies <b>Average Length</b>; <var>PREALLOCATED</var> implies <b>Fixed Length</b>.
<p>The meaning of the Length input field depends on data type and preallocation. FLOAT implies Precision. Otherwise, NON-PREALLOCATED implies Average Length; PREALLOCATED implies Fixed Length.</p>
<p>
<p>The Length input field is hidden when the data type is BINARY, because this data type has a predetermined length.</p>
The <b>Length</b> input field is hidden when the data type is <var>BINARY</var>, because this data type has a predetermined length.</p>
<p>PURE DBCS fields, if preallocated, require even values in the Length input field.</p>
<p>
<p>For Large Object (BLOB and CLOB) fields, the length of the actual object should be entered. If the Large Object data is larger than 9,999 bytes, use the Length Multiplier to enter a larger number.</p>
PURE DBCS fields, if preallocated, require even values in the <b>Length</b> input field.</p>
</td>
<p>
</tr>
For Large Object (<var>BLOB</var> and <var>CLOB</var>) fields, the length of the actual object should be entered. If the Large Object data is larger than 9,999 bytes, use the <b>Length Multiplier</b> to enter a larger number.</p></td></tr>
 
<tr>
<tr>
<td>Length Multiplier</td>
<td>Length Multiplier</td>
<td>Enables the ability to multiply a CLOB or BLOB field length by 100 if a value of H is entered; 1,000 if a value of T is entered; or by 1,000,000 if an M is entered.</td>
<td>Enables the ability to multiply a <var>CLOB</var> or <var>BLOB</var> field length by 100 if a value of <code>H</code> is entered; 1,000 if a value of <code>T</code> is entered; or by 1,000,000 if an <code>M</code> is entered.</td></tr>
</tr>
 
<tr>
<tr>
<td>Pad Character</td>
<td>Pad Character</td>
<td>This input field is available only when a field is preallocated and the Length attribute is also displayed. Otherwise, it is hidden.</td>
<td>This input field is available only when a field is preallocated and the <b>Length</b> attribute is also displayed. Otherwise, it is hidden.</td>
</tr>
</tr>
<tr>
<tr>
<td>Many-Valued/  
<td nowrap>Many-Valued/Few-Valued</td>
Few-Valued</td>
<td>This input field is available only in combination with the <var>CODED BINARY</var>, <var>CODED STRING</var>, and <var>CODED FLOAT</var> data types, or with <var>FRV</var>. Otherwise, it is hidden.
<td>
<p>
<p>This input field is available only in combination with the CODED BINARY, CODED STRING, and CODED FLOAT data types, or with FRV. Otherwise, it is hidden.</p>
The default is <var>MANY-VALUED</var>, as it is for the <var class="product">Model&nbsp;204</var> <var>DEFINE FIELD</var> command.</p></td></tr>
<p>The default is MANY-VALUED, as it is for the <var class="product">Model&nbsp;204</var> DEFINE FIELD command.</p>
 
</td>
</tr>
<tr>
<tr>
<td>At-Most-One/ Repeatable</td>
<td>At-Most-One/Repeatable</td>
<td>
<td>These mutually exclusive parameters must be selected by value cycling.
<p>These mutually exclusive parameters must be selected by value cycling.</p>
<p>
<p>Selecting AT-MOST-ONE hides the minimum and maximum input fields, which appear only if the input field value is REPEATABLE and not PREALLOCATED. If a REPEATABLE field is PREALLOCATED, use the REPEATABLE input field to indicate the number of occurrences to preallocate.</p>
Selecting <var>AT-MOST-ONE</var> hides the minimum and maximum input fields, which appear only if the input field value is <var>REPEATABLE</var> and not <var>PREALLOCATED</var>. If a <var>REPEATABLE</var> field is <var>PREALLOCATED</var>, use the <b>REPEATABLE</b> input field to indicate the number of occurrences to preallocate.</p>
<p>The default is REPEATABLE.</p>
<p>
</td>
The default is <var>REPEATABLE</var>.</p></td>
</tr>
</tr>
<tr>
<tr>
<td>Update in Place/
<td>Update in Place/Invisible</td>
Invisible</td>
<td>This input field combines two <var class="product">Model&nbsp;204</var> attributes: <var>VISIBLE/INVISIBLE</var> and <var>UPDATE IN PLACE/UPDATE AT END</var>. The values <var>UPD AT END</var> and <var>UPD IN PLACE</var> imply <var>INVISIBLE</var>.
<td>
<p>
<p>This input field combines two <var class="product">Model&nbsp;204</var> parameters: VISIBLE/INVISIBLE and UPDATE IN PLACE/UPDATE AT END. The values UPD AT END and UPD IN PLACE imply INVISIBLE.</p>
The value <var>INVISIBLE</var> is not permitted when the field is preallocated.</p>
<p>The value INVISIBLE is not permitted when the field is preallocated.</p>
<p>
<p>The default value is UPD IN PLACE.</p>
The default value is <var>UPD IN PLACE</var>.</p></td></tr>
</td>
 
</tr>
<tr>
<tr>
<td>Deferrable/
<td nowrap>Deferrable/Non-deferrable</td>
Non-deferrable</td>
<td>This input field is available only with <var>KEY</var>, <var>ORDERED</var>, or <var>NUMERIC RANGE</var>. Otherwise, it is hidden.
<td>
<p>
<p>This input field is available only with KEY, ORDERED, or NUMERIC RANGE. Otherwise, it is hidden.</p>
The default value is <var>DEFERRABLE</var>.</p></td></tr>
<p>The default value is DEFERRABLE.</p>
 
</td>
</tr>
<tr>
<tr>
<td>Min/Max Occurrences </td>
<td>Min/Max Occurrences </td>
<td>These range estimates are needed and displayed only for NON-PREALLOCATED fields.</td>
<td>These range estimates are needed and displayed only for <var>NON-PREALLOCATED</var> fields.</td></tr>
</tr>
 
<tr>
<tr>
<td>No. of Unique Values</td>
<td>No. of Unique Values</td>
<td>This optional input field is displayed when a field is CODED, KEY, ORDERED, FRV, or NUMERIC RANGE.</td>
<td>This optional input field is displayed when a field is <var>CODED</var>, <var>KEY</var>, <var>ORDERED</var>, <var>FRV</var>, or <var>NUMERIC RANGE</var>.</td>
</tr>
</tr>
<tr>
<tr>
<td>Key</td>
<td>Key</td>
<td>This input field is independent of all the others. The default value is NON-KEY.</td>
<td>This input field is independent of all the others. The default value is <var>NON-KEY</var>.</td>
</tr>
</tr>
<tr>
<tr>
<td>Ordered</td>
<td>Ordered</td>
<td>This input field is independent of all other input fields. The value attribute FRV is incompatible with ORDERED. NUMERIC RANGE is incompatible with ORDERED NUMERIC. The default is NON-ORDERED.</td>
<td>This input field is independent of all other input fields. The value attribute <var>FRV</var> is incompatible with <var>ORDERED</var>. <var>NUMERIC RANGE</var> is incompatible with <var>ORDERED NUMERIC</var>. The default is <var>NON-ORDERED</var>.</td>
</tr>
</tr>
<tr>
<tr>
<td>Unique</td>
<td>Unique</td>
<td>This input field is displayed only when KEY and NON-ORDERED have NON-FRV.</td>
<td>This input field is displayed only when <var>KEY</var> and <var>NON-ORDERED</var> have <var>NON-FRV</var>.</td>
</tr>
</tr>
<tr>
<tr>
<td>FRV (for each value)</td>
<td>FRV (for each value)</td>
<td>This input field is displayed only when KEY and NON-ORDERED have been selected. Otherwise, it is hidden. The default is NON-FRV.</td>
<td>This input field is displayed only when <var>KEY</var> and <var>NON-ORDERED</var> have been selected. Otherwise, it is hidden. The default is <var>NON-FRV</var>.</td>
</tr>
</tr>
<tr>
<tr>
<td>NUMERIC RANGE</td>
<td>NUMERIC RANGE</td>
<td>This input field is hidden if FLOAT or ORDERED NUM have been selected. The default is NON-NUMERIC RANGE.</td>
<td>This input field is hidden if <var>FLOAT</var> or <var>ORDERED NUM</var> have been selected. The default is <var>NON-NUMERIC RANGE</var>.</td>
</tr>
</tr>
<tr>
<tr>
<td>Significant Digits</td>
<td>Significant Digits</td>
<td>This input field is displayed only for NUMERIC RANGE fields. The default value is 1.</td>
<td>This input field is displayed only for <var>NUMERIC RANGE</var> fields. The default value is 1.</td>
</tr>
</tr>
<tr>
<tr>
<td>Access/204 descriptors</td>
<td>Access/204 descriptors</td>
<td>Applicable only to Access/204 users; dependencies are not enforced. However, warning messages are written.</td>
<td>Applicable only to Access/204 users; dependencies are not enforced. However, warning messages are written.</td>
</tr>
</tr>
<tr>
<tr>
<td>Ordered Field parameters</td>
<td>Ordered Field parameters</td>
<td>These parameters (Immediate, LRESERVE, and so on) appear only when either ORDERED NUM or ORDERED CHAR has been specified.</td>
<td>These parameters (Immediate, <var>LRESERVE</var>, and so on) appear only when either <var>ORDERED NUM</var> or <var>ORDERED CHAR</var> has been specified.</td>
</tr>
</tr>
<tr>
<tr>
<td>   LRESERVE</td>
<td>LRESERVE</td>
<td>
<td>Percentage of space to leave free on the left when a leaf-page splits during a deferred update or B-tree <code>REORGANIZE OI</code>.
<p>Percentage of space to leave free on the left when a leaf-page splits during a deferred update or B-tree REORGANIZE OI.</p>
<p>
<p>Valid values are 0 - 99. The default is 15.</p>
Valid values are 0 - 99. The default is 15.</p>
</td>
</td></tr>
</tr>
 
<tr>
<tr>
<td>   NRESERVE</td>
<td> NRESERVE</td>
<td>
<td>Percentage of space to leave free on the left when a node-page splits during a deferred update or B-tree <code>REORGANIZE OI</code>.
<p>Percentage of space to leave free on the left when a node-page splits during a deferred update or B-tree REORGANIZE OI.</p>
<p>
<p>Valid values are 0 - 99. The default is 15.</p>
Valid values are 0 - 99. The default is 15.</p></td></tr>
</td>
 
</tr>
<tr>
<tr>
<td>   SPLITPCT</td>
<td> SPLITPCT</td>
<td>
<td>Percentage of data to leave on the left when a page is split by an immediate update.
<p>Percentage of data to leave on the left when a page is split by an immediate update.</p>
<p>
<p>Valid values are 1 - 100. The default is 50.</p>
Valid values are 1 - 100. The default is 50.</p>
</td>
</td></tr>
</tr>
 
<tr>
<tr>
<td>   IMMED</td>
<td> IMMED</td>
<td>
<td>Immediate pointers per segment in B-tree. The value determines the number of instances that can be saved in the nodes of a B-tree rather than in a separate list.
<p>Immediate pointers per segment in B-tree. The value determines the number of instances that can be saved in the nodes of a B-tree rather than in a separate list.</p>
<p>
<p>Valid values are 0 - 255. The default is 1.</p>
Valid values are 0 - 255. The default is 1.</p>
</td>
</td></tr>
</tr>
 
<tr>
<tr>
<td>   SIZING PARAMETER</td>
<td> SIZING PARAMETER</td>
<td>
<td>Percentage of values that are directly added to the file (not via FLOD or deferred updates). The percentage is only a rough estimate such as 0, 50, 75, or 100.
<p>Percentage of values that are directly added to the file (not via FLOD or deferred updates). The percentage is only a rough estimate such as 0, 50, 75, or 100.</p>
<p>
<p>The value is used by file sizing as a weighting factor to estimate the relative significance of LRESERVE and SPLITPCT.</p>
The value is used by file sizing as a weighting factor to estimate the relative significance of <var>LRESERVE</var> and <var>SPLITPCT</var>.</p>
</td>
</td></tr>
</tr>
</table>
</table>
<b>Note</b>
<p class="note"><b>Note:</b>
<p>You can redefine the above tree structure parameters. The new values apply to the extensions of the tree, but not to the tree already in place. </p>
You can redefine the above tree structure parameters. The new values apply to the extensions of the tree, but not to the tree already in place. </p>
==Copying fields==
<p>Select the Copy Fields function (number 5) from the primary screen. </p>
<p>FILEMGMGT displays the Field Copy screen:</p>
<table>
<tr>
<td>
<p class="code"> FILEMGMT                Field Copy Screen
 
 
 
 
Filename:      ABC                                      Inactive
 
Fieldname:      ** All Fields **
 
 
Copy to FILE:
 
New Fieldname:  ** All Fields **
 
 
 
 
 


===>


1=HELp      2=          3=QUIt      4=          5=          6=
[[Category:FILEMGMT application subsystem]]
7=          8=          9=          10=          11=          12=END
</p></td>
</tr>
</table>
<p>&nbsp;</p>
<p>You use the Copy screen to copy one or more fields. The Copy can be to the same file (if just one field is copied) or to a different file. The fields can be either existing or staged.</p>
<p>A Copy operation is performed as soon as you leave the Copy screen. The copied fields are staged for the DEFINE command.</p>
<p>The cursor is initially positioned at the Field Name prompt.</p>
====Copy screen input====
<p>FILEMGMT displays or prompts you for the following information. </p>
<table>
<tr class="head">
<th>Prompt</th>
<th>Response</th>
</tr>
<tr>
<td>Filename </td>
<td> FILEMGMT displays the name of the file that you entered on the primary screen, and indicates whether the file is Active or Inactive.</td>
</tr>
<tr>
<td>Field Name</td>
<td>
<p>FILEMGMT displays the name of the field that you entered on the primary screen. If you did not enter a name on the primary screen, FILEMGMT displays: </p>
<p class="code"><b></b>** All Fields **   
</p></td>
</tr>
<tr>
<td>Copy to FILE </td>
<td>Type the name of the existing file to which FILEMGMT is to copy the field(s). This file can be the same as the file from which the copy is made, if you are not copying all fields.</td>
</tr>
<tr>
<td>New Fieldname or record on the primary screen:</td>
<td>
<p>If you entered a name for the source field:</p>
<b>Type the name of the new field to which FILEMGMT is to copy the source field. The field name cannot already exist.</b>
<ol>
<li>Press PF12 (END). FILEMGMT copies the field. </li>
</ol>
<p>If you did not enter a name for the source field on the primary screen, FILEMGMT displays the following message:</p>
<p class="code"><b></b>** All Fields **
</p>
<p>Do the following:</p>
<b>Do not type a new field name.</b>
<ol>
<li>Press PF12 (END). FILEMGMT copies all fields from one file to another. The copied fields have the same names as the original fields, but are prefixed (qualified) by the "Copy to FILE" name.</li>
</ol>
</td>
</tr>
</table>
<b>Note</b>
<p>A field is not copied to the target file if the file already contains a field with an unqualified name (name without the file name prefix) that is the same as the field name in the source file. FILEMGMT displays a WARNING MESSAGE when it copies all fields and finds entries with duplicate unqualified names. The WARNING MESSAGE indicates the number of fields that can be copied. </p>
<p>&nbsp;</p>
[[Category:File manager]]
[[Category:File management]]
[[Category:FILEMGMT Application Subsystem]]

Latest revision as of 04:20, 10 May 2014

Field attributes

To display the Field Attributes screens, choose one of the following methods:

  • Press the F11 (ATTributes) key from the Field Name List screen.
  • Select the Define or Redefine function from the primary screen and specify a particular field name. For Rename and Delete, you must first use the Field Name List screen.

FILEMGMT displays the Field Attributes screen shown on Field Attribute screen: initial defaults.

Proceeding to this screen stages either:

  • The fields you specified on the Field Name List screen
  • The field you specified on the primary screen for the function you selected on the primary screen.

You use the Field Attributes screen to specify or view values for field attributes. When the field attributes are displayed for a field for the first time, FILEMGMT shows the Model 204 default values. For existing or staged fields, FILEMGMT shows the current values.

The following field attributes cannot be redefined through FILEMGMT, because they can be redefined only if the file is reorganized:

  • Data type (STRING, BINARY, FLOAT, and so on.)
  • INVISIBLE
  • PREALLOCATED
  • LENGTH, OCCURS (if preallocated)
  • FEW-VALUED/MANY-VALUED (unless NONCODED and being redefined from non-FRV to FRV)

FILEMGMT displays screens for each field you specified on the Field Name List screen or the Field Attribute screen. The fields are displayed in the same order as on the Field Name List screen. You can advance to the next field by pressing the F11 (NEXtfld) key, or return to the previous field by pressing the F10 (PREvfld) key.

FILEMGMT does not save any of the information you enter until you press one of the following function keys from the screen:

F4 RECords
F6 COMmands
F10 PREvfld
F11 NEXtfld
F12 END

Only these PF keys verify data on the screen (F7 and F8 do not).

If you are deleting or renaming a field, the items on the Field Attributes screens are entry-protected and cannot be changed.

Field Attribute screen: initial defaults

The following screen shows the default values for FILEMGMT field attributes. This screen is displayed when you define a new field.

To change an attribute, you can either type over a highlighted value or position the cursor on a value cycling field and use F7 and F8 to display new values. When you change a value, the screen can change to reflect a variety of logical dependencies. New attributes appear, and incompatible attributes are hidden. For example, if you change the default value REPEATABLE to AT-MOST-ONE, the minimum and maximum Occurs input fields disappear (see Field Attribute Screen: Example 1 (NONORDERED, PREALLOCATED)).

The attributes related to ORDERED fields appear on the same screen as other attributes, and the Access/Target Descriptors (formerly called: physical format) are on a separate part of the screen.

FILEMGMT Field Attributes FILENAME: VEHICLES FIELDNAME: MY DATE TIME STAMP FIELD NAME CONTAINING SPACES Data Type NON-PREALLOCATED Average Length Security STRING REPEATABLE in Bytes 20__ LVL: 0__ UPD IN PLACE MIN. OCCURS 1__ NO. OF UNIQUE MAX. OCCURS 1__ VALUES: ________ NON-KEY NON-ORDERED ===== ACCESS/TARGET Descriptors ===== NON-NUMERIC-RANGE Picture Format FIXED X(20)_______ NO MIXED CASE ===> 1=HELp 2= 3=QUIt 4=RECords 5=COPy 6=COMmands 7=PREv value 8=NEXt value 9=SIZe 10=PRVfield 11=NXTfield 12=END

The date-time stamp field:

  • Must be STRING; and Rocket Software recommends the ORDERED CHARACTER attribute.
  • Cannot be defined as INVISIBLE.
  • Cannot be a multiply occurring field.
  • Can be preallocated.

Field Attribute Screen: Example 1 (NONORDERED, PREALLOCATED)

The following example shows what happens when you change the attributes to NONORDERED, PREALLOCATED, and KEY.

Notice that Average Length becomes Fixed length; the Pad Char input field appears; an occurrence count input field follows REPEATABLE; and the MIN. OCCURS and MAX. OCCURS input fields are hidden. These are examples of dynamic screen management, described more fully in Field attribute dependency rules.

FILEMGMT Field Attributes FILENAME: ABC FIELDNAME: ABCFIELD Data Type PREALLOCATED Fixed Length Security STRING REPEATABLE 1__ in Bytes ____ LVL: 0__ UPD IN PLACE NO. OF UNIQUE VALUES:________ KEY NON-ORDERED ===== ACCESS/TARGET Descriptors ===== FRV NON-NUMERIC-RANGE Picture Format FIXED MANY VALUED X(20)_______ NO MIXED CASE ===> 1=HELp 2= 3=QUIt 4=RECords 5=COPy 6=COMmands 7=PREv value 8=NEXt value 9=SIZe 10= 11= 12=END

Field Attribute Screen: Example 2 (ORDERED)

When you specify an ORDERED field, a new set of parameters appears at the bottom of the screen.

Notice that the NON-UNIQUE attribute appears, while the FRV attribute has been hidden.

FILEMGMT Field Attributes FILENAME: ABC FIELDNAME: ABCFIELD Data Type NON-PREALLOCATED Average Length Security STRING REPEATABLE in Bytes ____ LVL: 0__ UPD IN PLACE MIN. OCCURS 1__ NO. OF UNIQUE MAX. OCCURS 1__ VALUES:________ NON-KEY ORDERED CHAR NON-UNIQUE ==== ACCESS/TARGET Descriptors ===== NON-NUMERIC-RANGE Picture Format FIXED X(20)_______ NO MIXED CASE ==================== Parameters for Ordered Index===================== IMMED: 1 LRESERVE: 15% SIZING PARAMETER: THE PERCENTAGE OF (PTRS TO TABLE-B NRESERVE: 15% THE VALUES TO BE DDED DIRECTLY, NOT IN LEAF ENTRY) SPLITPCT: 50% BY DEFERRED UPDATE) 50% ===> 1=HELp 2= 3=QUIt 4=RECords 5=COPy 6=COMmands 7=PREv value 8=NEXt value 9=SIZe 10= 11= 12=END

Field Attribute screen input

Based on the command and your entry point, you have the following options for changing information on the screen:

  • DEFINE/REDEFINE

    You can change the field name if you entered the Field Attributes screen from the primary screen to define a field. Otherwise, you cannot change the field name.

    You can type over the values of any of the attributes if the field is staged for DEFINE. Some attributes are entry-protected if the field is staged for REDEFINE.

Note: Requesting a field REDEFINE that changes the average length of a non-preallocated field might generate a record REDEFINE command for each record that the field cross-references. Each record's average length is readjusted to reflect the difference between the old and new average length multiplied by the field percent rate for the record.

  • DELETE/RENAME

    You can view but not change any information on this screen.

Field Attribute screen commands

To issue a command, press a PF key or type a command name at the prompt (===>), and press Enter.

Key Command Meaning
F1 HELP Displays HELp text for the Field Attributes screen.
F3 QUIt Exits from the Field Attributes screen and returns to the previous screen without making any changes to the current field.
F4 RECords Proceeds to the Record Name List screen. This screen lists the records in the file. Changes to the current field are saved in the dictionary.
F5 COPY This PF key allows you to copy attribute values from an existing field to a field being defined or redefined. To execute the COPY command, enter the qualified or unqualified name of the source field on the command line and press F2. All parameter values are then copied to the field being defined. This option is valid only for defining a field.

If you specify the fully-qualified field name, you can then copy attributes from fields in external files, provided that the external files are defined in the Model 204 dictionary.

F6 COMmands Proceeds to the Execute Commands screen. This screen displays the staged commands that were generated for the file and allows you to select the commands you want to execute. Changes to the current field are saved in the dictionary.
F7 NEXt value Scrolls forward through the valid values of a particular cycling input field. When there are logical conflicts between attributes, cycling values can cause other attribute input fields to be hidden or revealed.
F8 PREv value Scrolls backward through the values of a cycling input field.
F9 SIZe Proceeds to the File Size Definition screen. This screen displays information about the size of the file. Changes to the current field are saved in the dictionary.
F10 PREvfld Displays the previous field, defined by the order in which fields were selected on the Field Name List screen. Changes to the current field are saved in the dictionary.
F11 NEXtfld Displays the next field, defined by the order in which fields were selected on the Field Name List screen. Changes to the current field are saved in the dictionary.
F12 END Exits from the Field Attributes screen and returns to your entry point (Field Name List screen or primary screen). Changes to the current field are saved in the dictionary.

Abbreviations

Another time-saving device is an extensive set of abbreviations for field attribute values. For example, you can type NP, NPRE, or NON when specifying the NON-PREALLOCATED attribute.

Note: Some abbreviations (such as NON) are valid for several different attributes. When using such abbreviations, take careful note of which field attribute on the screen you are changing.

The following table lists value-cycling input fields and their abbreviations on the Field Attribute screen:

Value-cycling input fields and abbreviations
Cycled values Valid abbreviations
PREALLOCATED
NON-PREALLOCATED
P, PRE, ALLOC
NP, NPRE, NON
STRING
CODED STRING
BINARY
CODED BINARY
FLOAT
CODED FLOAT
PURE DBCS
MIXED DBCS
CLOB
BLOB
S, STR
CS, CSTR, CDSTR
B, BIN
CB, CBIN, CDBIN
F, FLT
CF, CFL, CDFL
K, KANJI, DBCS
M, MIXED, MIX
CL, CLOB, CHARLOB
BL, BLOB, BINLOB
FEW VALUED
MANY VALUED
F, FV, FEW
M, MV, MANY
AT-MOST-ONE
REPEATABLE
O, AT, ONE
R, RP, REPT
INVISIBLE
UPD IN PLACE
UPD AT END
I, INV, INVIS
UP, UIP
UE, UAE
DEFERRABLE
NON-DEFERRABLE
D, DEF
ND, NON, NDEF
KEY
NON-KEY
K
NK, NON, NKEY
ORDERED CHAR
ORDERED NUM
NON-ORDERED
OC, ORDC, ORD
ON, ORDN
NO, NON, NORD
UNIQUE
NON-UNIQUE
U, UN, UNIQ
NU, NON, NUNIQ
NUMERIC RANGE
NON NUMERIC RANGE
NR, RANGE
NNR, NON
FRV
NON-FRV
F
NF, NON, NFRV
FIXED
VARIABLE
F, FIX
V, VAR
LEADING ZEROS
TRAILING ZEROS
LEADING AND TRAILING ZEROS
NO LEADING OR TRAILING ZEROS
MIXED CASE
NO MIXED CASE
L, LZ
T, TZ
LT, LTZ
NLT, NLTZ
M, MIXED, MIX
NM, NOMIX, UPPER

Field attribute dependency rules

As the examples show, the Field Attributes screen features dynamic screen management, based on a set of dependency rules governing logical relations among attributes. The dependency rules are listed here for each attribute. For complete descriptions of file parameters, refer to List of Model 204 parameters.

Attribute Rules
Security Level Independent of all other input fields. The default value is zero, indicating that field-level security is not in effect. Maximum value is 255.
Data Type Independent of all other input fields. However, this string attribute includes the values CODED STRING, CODED BINARY, and CODED FLOAT to enforce the association of CODED with one of these three data types.

The double-byte character set (DBCS) parameters are allowed only when the system parameter DBCSENV indicates that DBCS is supported at your site.

Preallocated/Non PREALLOCATED means that space is reserved in Table B for the field. Use the REPEATABLE input field to indicate the number of occurrences to preallocate. PREALLOCATED implies Fixed Length and conflicts with the attribute INVISIBLE.

The default setting is NON-PREALLOCATED, in which case the number of occurrences cannot be entered in the REPEATABLE input field. For Large Object (CLOB) or BLOB) fields, preallocation refers only to the pointer entry stored in Table B for a Large Object field. The pointer entry is 27 bytes for each preallocated Large Object field and 30 bytes for each non-preallocated field.

Length The meaning of the Length input field depends on data type and preallocation. FLOAT implies Precision. Otherwise, NON-PREALLOCATED implies Average Length; PREALLOCATED implies Fixed Length.

The Length input field is hidden when the data type is BINARY, because this data type has a predetermined length.

PURE DBCS fields, if preallocated, require even values in the Length input field.

For Large Object (BLOB and CLOB) fields, the length of the actual object should be entered. If the Large Object data is larger than 9,999 bytes, use the Length Multiplier to enter a larger number.

Length Multiplier Enables the ability to multiply a CLOB or BLOB field length by 100 if a value of H is entered; 1,000 if a value of T is entered; or by 1,000,000 if an M is entered.
Pad Character This input field is available only when a field is preallocated and the Length attribute is also displayed. Otherwise, it is hidden.
Many-Valued/Few-Valued This input field is available only in combination with the CODED BINARY, CODED STRING, and CODED FLOAT data types, or with FRV. Otherwise, it is hidden.

The default is MANY-VALUED, as it is for the Model 204 DEFINE FIELD command.

At-Most-One/Repeatable These mutually exclusive parameters must be selected by value cycling.

Selecting AT-MOST-ONE hides the minimum and maximum input fields, which appear only if the input field value is REPEATABLE and not PREALLOCATED. If a REPEATABLE field is PREALLOCATED, use the REPEATABLE input field to indicate the number of occurrences to preallocate.

The default is REPEATABLE.

Update in Place/Invisible This input field combines two Model 204 attributes: VISIBLE/INVISIBLE and UPDATE IN PLACE/UPDATE AT END. The values UPD AT END and UPD IN PLACE imply INVISIBLE.

The value INVISIBLE is not permitted when the field is preallocated.

The default value is UPD IN PLACE.

Deferrable/Non-deferrable This input field is available only with KEY, ORDERED, or NUMERIC RANGE. Otherwise, it is hidden.

The default value is DEFERRABLE.

Min/Max Occurrences These range estimates are needed and displayed only for NON-PREALLOCATED fields.
No. of Unique Values This optional input field is displayed when a field is CODED, KEY, ORDERED, FRV, or NUMERIC RANGE.
Key This input field is independent of all the others. The default value is NON-KEY.
Ordered This input field is independent of all other input fields. The value attribute FRV is incompatible with ORDERED. NUMERIC RANGE is incompatible with ORDERED NUMERIC. The default is NON-ORDERED.
Unique This input field is displayed only when KEY and NON-ORDERED have NON-FRV.
FRV (for each value) This input field is displayed only when KEY and NON-ORDERED have been selected. Otherwise, it is hidden. The default is NON-FRV.
NUMERIC RANGE This input field is hidden if FLOAT or ORDERED NUM have been selected. The default is NON-NUMERIC RANGE.
Significant Digits This input field is displayed only for NUMERIC RANGE fields. The default value is 1.
Access/204 descriptors Applicable only to Access/204 users; dependencies are not enforced. However, warning messages are written.
Ordered Field parameters These parameters (Immediate, LRESERVE, and so on) appear only when either ORDERED NUM or ORDERED CHAR has been specified.
LRESERVE Percentage of space to leave free on the left when a leaf-page splits during a deferred update or B-tree REORGANIZE OI.

Valid values are 0 - 99. The default is 15.

NRESERVE Percentage of space to leave free on the left when a node-page splits during a deferred update or B-tree REORGANIZE OI.

Valid values are 0 - 99. The default is 15.

SPLITPCT Percentage of data to leave on the left when a page is split by an immediate update.

Valid values are 1 - 100. The default is 50.

IMMED Immediate pointers per segment in B-tree. The value determines the number of instances that can be saved in the nodes of a B-tree rather than in a separate list.

Valid values are 0 - 255. The default is 1.

SIZING PARAMETER Percentage of values that are directly added to the file (not via FLOD or deferred updates). The percentage is only a rough estimate such as 0, 50, 75, or 100.

The value is used by file sizing as a weighting factor to estimate the relative significance of LRESERVE and SPLITPCT.

Note: You can redefine the above tree structure parameters. The new values apply to the extensions of the tree, but not to the tree already in place.