RENAME FIELD command: Difference between revisions
m (Automatically generated page update) |
No edit summary |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
<b>Where:</b> | <b>Where:</b> | ||
old-fieldname and new-fieldname are field names (1 to 255 characters). When the command is executed, the new fieldname becomes the new name of the field. | <var class="term">old-fieldname</var> and <var class="term">new-fieldname</var> are field names (1 to 255 characters). When the command is executed, the new fieldname becomes the new name of the field. | ||
===Syntax notes=== | ===Syntax notes=== | ||
The comma is required. | The comma is required. | ||
==Example== | ==Example== | ||
<p class="code">RENAME FIELD SOCIAL SECURITY, SSN | <p class="code">RENAME FIELD SOCIAL SECURITY, SSN | ||
</p> | </p> | ||
==Usage notes== | ==Usage notes== | ||
<p>The RENAME FIELD command changes the name of a field. The command is rejected if the old field name does not exist or if the new field name cannot be added to the file, either because it already exists or because there is not enough space. RENAME FIELD can be used to rename Ordered Index fields. </p> | <p>The RENAME FIELD command changes the name of a field. The command is rejected if the old field name does not exist or if the new field name cannot be added to the file, either because it already exists or because there is not enough space. RENAME FIELD can be used to rename Ordered Index fields, as well as ORDERED INVISIBLE fields. </p> | ||
<p>When it processes RENAME FIELD, <var class="product">Model 204</var> ends any update unit in progress and begins a non-backoutable update unit. | <p>When it processes RENAME FIELD, <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> | ||
< | Restrictions on renaming: | ||
<p class="code">M204.2727: CANT DELETE DTS FIELD WHEN FOPT=X'10' IS ON | <ul> | ||
</ | <li>The RENAME FIELD command is prohibited for the DTSFN field in a file when the FOPT=X'10' is set. Attempting to do so results in the following message: | ||
<p class="code">M204.2727: CANT DELETE DTS FIELD WHEN FOPT=X'10' IS ON</p> | |||
</li> | |||
<li>Renaming of [[DEFINE_FIELD_command#CHUNK_attribute|OI chunk]] and OI chunk target fields is not allowed.</li> | |||
</ul> | |||
[[Category: File manager commands]] | [[Category: File manager commands]] | ||
[[Category:Commands]] | [[Category:Commands]] | ||
Latest revision as of 22:40, 11 December 2013
Summary
- Privileges
- File manager
- Function
- Changes the name of a field
Syntax
RENAME FIELD old-fieldname, new-fieldname
Where: old-fieldname and new-fieldname are field names (1 to 255 characters). When the command is executed, the new fieldname becomes the new name of the field.
Syntax notes
The comma is required.
Example
RENAME FIELD SOCIAL SECURITY, SSN
Usage notes
The RENAME FIELD command changes the name of a field. The command is rejected if the old field name does not exist or if the new field name cannot be added to the file, either because it already exists or because there is not enough space. RENAME FIELD can be used to rename Ordered Index fields, as well as ORDERED INVISIBLE fields.
When it processes RENAME FIELD, Model 204 ends any update unit in progress and begins a non-backoutable update unit.
Restrictions on renaming:
- The RENAME FIELD command is prohibited for the DTSFN field in a file when the FOPT=X'10' is set. Attempting to do so results in the following message:
M204.2727: CANT DELETE DTS FIELD WHEN FOPT=X'10' IS ON
- Renaming of OI chunk and OI chunk target fields is not allowed.