REDEFINE command - Revision history

JAL: link repair

2015-08-03T18:22:06Z

link repair

← Older revision		Revision as of 18:22, 3 August 2015
Line 171:		Line 171:
	If a field already is defined as <var>ORDERED</var>, the <var>REDEFINE</var> command can change the related attributes by specifying the attribute and a new value. A change to the <var>LRESERVE</var>, <var>NRESERVE</var>, <var>SPLITPCT</var>, or <var>IMMED</var> attribute does not cause any change to the existing Ordered Index but modifies the effect of any updates.</p>		If a field already is defined as <var>ORDERED</var>, the <var>REDEFINE</var> command can change the related attributes by specifying the attribute and a new value. A change to the <var>LRESERVE</var>, <var>NRESERVE</var>, <var>SPLITPCT</var>, or <var>IMMED</var> attribute does not cause any change to the existing Ordered Index but modifies the effect of any updates.</p>
	<p>		<p>
	Refer to the discussion in [[DEFINE FIELD command~~\|DEFINE FIELD: Field names and attributes~~]] for more information on the Ordered Index field attributes.</p>		Refer to the discussion in [[DEFINE FIELD command]] for more information on the Ordered Index field attributes.</p>
	<p>		<p>
	The following example eliminates the Ordered Index for the <code>TAX</code> field: </p>		The following example eliminates the Ordered Index for the <code>TAX</code> field: </p>

JAL at 16:10, 16 April 2015

2015-04-16T16:10:53Z

← Older revision		Revision as of 16:10, 16 April 2015
Line 32:		Line 32:

	<table class="thJustBold">		<table class="thJustBold">
	~~<caption> Field description attributes </caption>~~
	<tr class="head">		<tr class="head">
	<th><p>Field description attribute</p>		<th><p>Field description attribute</p>

JAL: misc cleanup

2015-04-16T16:09:54Z

misc cleanup

Show changes

JAL: misc cleanup

2015-04-16T15:45:51Z

misc cleanup

← Older revision		Revision as of 15:45, 16 April 2015
Line 16:		Line 16:
	<tr>		<tr>
	<th nowrap>field-description</th>		<th nowrap>field-description</th>
	<td> ~~takes~~ the following form:		<td>Takes the following form:
	<p class="code"><i>fieldname</i> [(<i>attribute</i> [<i>attribute</i>]...)]		<p class="code"><i>fieldname</i> [(<i>attribute</i> [<i>attribute</i>]...)]
	</p></td>		</p></td>
Line 23:		Line 23:
	<tr>		<tr>
	<th>fieldname</th>		<th>fieldname</th>
	<td> (1 to 255 characters) ~~is the name~~ of a field in the open <var class="product">Model 204</var> file.</td>		<td>The name (1 to 255 characters) of a field in the open <var class="product">Model 204</var> file.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th>attribute</th>		<th>attribute</th>
	<td> ~~is one~~ of those listed in the table below. All attributes are described in detail in [[DEFINE FIELD command]] and [[Field design]].		<td>One of those listed in the table below. All attributes are described in detail in [[DEFINE FIELD command]] and [[Field design]].

	<table class="thJustBold">		<table class="thJustBold">

ELowell: /* Syntax */

2014-09-02T17:12:23Z

Syntax

← Older revision		Revision as of 17:12, 2 September 2014
Line 28:		Line 28:
	<tr>		<tr>
	<th>attribute</th>		<th>attribute</th>
	<td> is one of those listed in the table below. All attributes are described in detail in ~~the <var class="book">Model 204 File Manager's Guide</var>~~.		<td> is one of those listed in the table below. All attributes are described in detail in [[DEFINE FIELD command]] and [[Field design]].

	<table class="thJustBold">		<table class="thJustBold">

JAL: /* Syntax notes */

2014-02-25T01:21:53Z

Syntax notes

← Older revision		Revision as of 01:21, 25 February 2014
Line 124:		Line 124:
	<li>If <var>FIELD</var> is specified, or if the <var>WITH</var> form of the <var>REDEFINE</var> command is used, only one field can be redefined; otherwise, multiple fields can be redefined.</li>		<li>If <var>FIELD</var> is specified, or if the <var>WITH</var> form of the <var>REDEFINE</var> command is used, only one field can be redefined; otherwise, multiple fields can be redefined.</li>

	<li>The attributes must be enclosed in parentheses unless WITH is specified.		<li>The attributes must be enclosed in parentheses unless <var>WITH</var> is specified.
	<p>		<p>
	Attributes must be separated by commas or by one or more blanks.</p></li>		Attributes must be separated by commas or by one or more blanks.</p></li>

JAL: /* Syntax */

2014-02-25T01:21:16Z

Syntax

Show changes

JAL: /* Syntax */

2014-02-24T23:48:37Z

Syntax

← Older revision		Revision as of 23:48, 24 February 2014
Line 15:		Line 15:
	<table>		<table>
	<tr>		<tr>
	<th>field-description</th>		<th nowrap>field-description</th>
	<td> takes the following form:		<td> takes the following form:
	<p class="code"><i>fieldname</i> [(<i>attribute</i> [<i>attribute</i>]...)]		<p class="code"><i>fieldname</i> [(<i>attribute</i> [<i>attribute</i>]...)]
Line 32:		Line 32:
	<caption> Field description attributes </caption>		<caption> Field description attributes </caption>

	<tr> <th>		<tr class="head">
	<p>Field description attribute</p>		<th><p>Field description attribute</p>
	</th> <th>		</th>
	<p>Abbreviation</p>		<th><p>Abbreviation</p>
	</th> </tr>		</th> </tr>

Line 62:		Line 62:
	</td> </tr>		</td> </tr>

	<tr> <th><var>		<tr> <th><var><p>FEW-VALUED *</p></var></th>
	<p>FEW-VALUED *</p>		<td><p>FV</p>
	</var></th> <td>
	<p>FV</p>
	</td> </tr>		</td> </tr>

Line 150:		Line 148:
	</var></th> <td>		</var></th> <td>
	<p>UE</p>		<p>UE</p>
	</td> </tr>		</td> </tr>

	</table>		</table>

	<p>* You can specify FEW-VALUED and MANY-VALUED only if a field is being redefined from NON-FRV NON-CODED to FRV NON-CODED.</p>		<p>* You can specify FEW-VALUED and MANY-VALUED only if a field is being redefined from NON-FRV NON-CODED to FRV NON-CODED.</p>
	</td>		</td>
	</tr>		</tr>

	</table>		</table>

	===Syntax notes===		===Syntax notes===
	<p>If FIELD is specified or the WITH form of the REDEFINE command is used, only one field can be redefined; otherwise, multiple fields can be redefined.</p>		<p>If FIELD is specified or the WITH form of the REDEFINE command is used, only one field can be redefined; otherwise, multiple fields can be redefined.</p>
Line 163:		Line 161:
	<p>Attributes must be separated by commas or by one or more blanks.</p>		<p>Attributes must be separated by commas or by one or more blanks.</p>
	<p>REDEFINE can be specified only in file context.</p>		<p>REDEFINE can be specified only in file context.</p>

	==Example==		==Example==
	<p class="code">REDEFINE SOC SEC (KEY,NR,LEVEL 0)		<p class="code">REDEFINE SOC SEC (KEY,NR,LEVEL 0)

ELowell at 22:39, 11 December 2013

2013-12-11T22:39:21Z

← Older revision		Revision as of 22:39, 11 December 2013
Line 211:		Line 211:

	====Update units====		====Update units====
	<p>When it processes REDEFINE, <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable [[File ~~Integrity~~ and ~~Recovery~~#Update units and transactions\|update unit]].</p>		<p>When it processes REDEFINE, <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable [[File integrity and recovery#Update units and transactions\|update unit]].</p>

	====Redefining Large Object fields====		====Redefining Large Object fields====

JDamon: /* Redefining CHUNK fields */

2013-10-11T17:52:09Z

Redefining CHUNK fields

← Older revision		Revision as of 17:52, 11 October 2013
Line 198:		Line 198:
	<p class="code">REDEFINE EXPENSE (IMMED 20)		<p class="code">REDEFINE EXPENSE (IMMED 20)
	</p>		</p>
	====Redefining CHUNK fields====		====Redefining OI CHUNK fields====
	Redefining OI chunk fields or OI chunk target fields is not allowed.		Redefining OI chunk fields or OI chunk target fields is not allowed.