Managing fields manually - Revision history

JAL: link repair

2017-04-07T21:21:48Z

link repair

← Older revision		Revision as of 21:21, 7 April 2017
Line 171:		Line 171:
	===Redefining fields with security levels===		===Redefining fields with security levels===
	<p>		<p>
	If a field that is being redefined has a security level defined for it (see [[~~Security~~]]), you must have a field security level that permits some type of access.</p>		If a field that is being redefined has a security level defined for it (see [[Model 204 security features]]), you must have a field security level that permits some type of access.</p>

	==Monitoring field retrievals==		==Monitoring field retrievals==

JALWiccan: Automatically generated page update

2017-04-07T21:17:06Z

Automatically generated page update

← Older revision		Revision as of 21:17, 7 April 2017
Line 147:		Line 147:

	<p>		<p>
	Changing a field's security level to 0 desecures the field. Refer to [[~~Security~~#Field-level security\|Field-level security]] for more information.</p>		Changing a field's security level to 0 desecures the field. Refer to [[Model 204 security features#Field-level security\|Field-level security]] for more information.</p>

	<p class="note"><b>Note:</b> Redefining fields may take a substantial amount of CPU time. When a <var>KEY</var>, <var>NUMERIC RANGE</var>, or <var>ORDERED</var> attribute is changed for a <var>VISIBLE</var> field, <var class="product">Model 204</var> must modify the index entries that correspond to each occurrence of the field in Table B. </p>		<p class="note"><b>Note:</b> Redefining fields may take a substantial amount of CPU time. When a <var>KEY</var>, <var>NUMERIC RANGE</var>, or <var>ORDERED</var> attribute is changed for a <var>VISIBLE</var> field, <var class="product">Model 204</var> must modify the index entries that correspond to each occurrence of the field in Table B. </p>
Line 210:		Line 210:
	<var class="term">fieldname</var> is the name assigned when the field was defined. </p>		<var class="term">fieldname</var> is the name assigned when the field was defined. </p>
	<p>		<p>
	A <var>DELETE FIELD</var> command cannot be used to delete record security fields or sort and hash key fields. If the field being deleted is in a file that has record security, you must have record security override privileges (see [[~~Security~~#Record security\|record security]]). If the field has a security level defined for it, you must have a field-level security level that permits update access.</p>		A <var>DELETE FIELD</var> command cannot be used to delete record security fields or sort and hash key fields. If the field being deleted is in a file that has record security, you must have record security override privileges (see [[Model 204 security features#Record security\|record security]]). If the field has a security level defined for it, you must have a field-level security level that permits update access.</p>
	<p>		<p>
	Other uses of the <var>DELETE</var> command are accessible via the [[:Category:Commands\|Commands category]], specifically for:</p>		Other uses of the <var>DELETE</var> command are accessible via the [[:Category:Commands\|Commands category]], specifically for:</p>
Line 240:		Line 240:
	If a TABLE C FULL condition occurs during the renaming of a <var>KEY</var> or <var>NUMERIC RANGE</var> field, the file is left in a broken state. This happens even if the file is a transaction back out file. To prevent this condition, issue a <var>TABLEC</var> command to check for available space, or back up the file before renaming a field, or do both of these. </p>		If a TABLE C FULL condition occurs during the renaming of a <var>KEY</var> or <var>NUMERIC RANGE</var> field, the file is left in a broken state. This happens even if the file is a transaction back out file. To prevent this condition, issue a <var>TABLEC</var> command to check for available space, or back up the file before renaming a field, or do both of these. </p>
	<p>		<p>
	Record security fields and sort and hash key fields can be renamed. If a field that is being renamed has a security level defined for it (see [[~~Security~~#Field-level security\|Field-level security]]), you must have a field security level that permits some type of access.</p>		Record security fields and sort and hash key fields can be renamed. If a field that is being renamed has a security level defined for it (see [[Model 204 security features#Field-level security\|Field-level security]]), you must have a field security level that permits some type of access.</p>
	<p>		<p>
	The <var>RENAME</var> command cannot be used to rename an <var>INVISIBLE</var> field. If you do want to rename an <var>INVISIBLE</var> field, delete all occurrences of the old field and then add them to the record under the new name. </p>		The <var>RENAME</var> command cannot be used to rename an <var>INVISIBLE</var> field. If you do want to rename an <var>INVISIBLE</var> field, delete all occurrences of the old field and then add them to the record under the new name. </p>

JAL at 17:45, 30 October 2014

2014-10-30T17:45:10Z

← Older revision		Revision as of 17:45, 30 October 2014
Line 225:		Line 225:
	==Renaming fields==		==Renaming fields==
	<p>		<p>
	The <var>[[RENAME command\|RENAME]]</var> command and the <var>IFNFLD</var> Host Language Interface function allow you to rename a field. The command is issued in the form:</p>		The <var>[[RENAME FIELD command\|RENAME]]</var> command and the <var>IFNFLD</var> Host Language Interface function allow you to rename a field. The command is issued in the form:</p>
	<b>Syntax</b>		<b>Syntax</b>
	<p class="syntax">RENAME FIELD <span class="term">oldname</span>,<span class="term">newname</span>		<p class="syntax">RENAME FIELD <span class="term">oldname</span>,<span class="term">newname</span>

JAL at 21:33, 14 August 2014

2014-08-14T21:33:24Z

← Older revision		Revision as of 21:33, 14 August 2014
Line 3:		Line 3:
	This page describes the <var>[[REDEFINE command\|REDEFINE]]</var>, <var>[[DELETE command: Field\|DELETE]]</var>, and <var>[[RENAME FIELD command\|RENAME]]</var> commands, which allow you to redefine many field attributes, to delete a field's description and all its occurrences in the data, and to rename fields. For the complete syntax and description of these commands, please follow the links.</p>		This page describes the <var>[[REDEFINE command\|REDEFINE]]</var>, <var>[[DELETE command: Field\|DELETE]]</var>, and <var>[[RENAME FIELD command\|RENAME]]</var> commands, which allow you to redefine many field attributes, to delete a field's description and all its occurrences in the data, and to rename fields. For the complete syntax and description of these commands, please follow the links.</p>

	<p class="note">'''Note:''' New fields and Repeating Field Groups may may be added by the file manager at any time (although some attributes may not be assigned to these new fields (such as the [[Field design#Preallocated fields (OCCURS attribute)\|OCCurs attribute]] to preallocate a field) once data has been added to the file. See [[~~Field design\|~~Field design]] for more details.)</p>		<p class="note">'''Note:''' New fields and Repeating Field Groups may may be added by the file manager at any time (although some attributes may not be assigned to these new fields (such as the [[Field design#Preallocated fields (OCCURS attribute)\|OCCurs attribute]] to preallocate a field) once data has been added to the file. See [[Field design]] for more details.)</p>

	<p>		<p>

JAL: /* Field attributes and the REDEFINE command */

2014-08-14T21:32:30Z

Field attributes and the REDEFINE command

← Older revision		Revision as of 21:32, 14 August 2014
Line 51:		Line 51:
	====Field attributes and the REDEFINE command====		====Field attributes and the REDEFINE command====
	<p>		<p>
	Not all the field attributes that can be specified in the DEFINE command can be changed by a REDEFINE command. The following table summarizes the options.</p>		Not all the field attributes that can be specified in the <var>DEFINE</var> command can be changed by a <var>REDEFINE</var> command. The following table summarizes the options.</p>
	<p>		<p>
	See [[ ~~Field design\|~~Field design]] for a full discussion of the classifications and attributes.</p>		See [[Field design]] for a full discussion of the classifications and attributes.</p>

	<table>		<table>

ELowell at 16:49, 12 May 2014

2014-05-12T16:49:34Z

← Older revision		Revision as of 16:49, 12 May 2014
Line 3:		Line 3:
	This page describes the <var>[[REDEFINE command\|REDEFINE]]</var>, <var>[[DELETE command: Field\|DELETE]]</var>, and <var>[[RENAME FIELD command\|RENAME]]</var> commands, which allow you to redefine many field attributes, to delete a field's description and all its occurrences in the data, and to rename fields. For the complete syntax and description of these commands, please follow the links.</p>		This page describes the <var>[[REDEFINE command\|REDEFINE]]</var>, <var>[[DELETE command: Field\|DELETE]]</var>, and <var>[[RENAME FIELD command\|RENAME]]</var> commands, which allow you to redefine many field attributes, to delete a field's description and all its occurrences in the data, and to rename fields. For the complete syntax and description of these commands, please follow the links.</p>

	<p class="note">'''Note:''' New fields and Repeating Field Groups may may be added by the file manager at any time (although some attributes may not be assigned to these new fields (such as the [[Field design ~~(File management)~~#Preallocated fields (OCCURS attribute)\|OCCurs attribute]] to preallocate a field) once data has been added to the file. See [[Field design ~~(File management)~~\|Field design]] for more details.)</p>		<p class="note">'''Note:''' New fields and Repeating Field Groups may may be added by the file manager at any time (although some attributes may not be assigned to these new fields (such as the [[Field design#Preallocated fields (OCCURS attribute)\|OCCurs attribute]] to preallocate a field) once data has been added to the file. See [[Field design\|Field design]] for more details.)</p>

	<p>		<p>
Line 53:		Line 53:
	Not all the field attributes that can be specified in the DEFINE command can be changed by a REDEFINE command. The following table summarizes the options.</p>		Not all the field attributes that can be specified in the DEFINE command can be changed by a REDEFINE command. The following table summarizes the options.</p>
	<p>		<p>
	See [[ Field design ~~(File management)~~\|Field design]] for a full discussion of the classifications and attributes.</p>		See [[ Field design\|Field design]] for a full discussion of the classifications and attributes.</p>

	<table>		<table>

DmeWiccan: Automatically generated page update

2014-05-09T22:45:51Z

Automatically generated page update

← Older revision		Revision as of 22:45, 9 May 2014
Line 246:		Line 246:
	Because of this danger, and because, on larger files the scan of Table B to change the field identifier may be lengthy (and, if renaming multiple fields are done one per pass), you may want to consider [[File reorganization and table compaction\|reorganizing the file]] to rename fields.</p>		Because of this danger, and because, on larger files the scan of Table B to change the field identifier may be lengthy (and, if renaming multiple fields are done one per pass), you may want to consider [[File reorganization and table compaction\|reorganizing the file]] to rename fields.</p>

	[[Category:~~File management~~]]		[[Category:Model 204 files]]

JALWiccan: Automatically generated page update

2014-04-17T21:00:11Z

Automatically generated page update

← Older revision		Revision as of 21:00, 17 April 2014
Line 3:		Line 3:
	This page describes the <var>[[REDEFINE command\|REDEFINE]]</var>, <var>[[DELETE command: Field\|DELETE]]</var>, and <var>[[RENAME FIELD command\|RENAME]]</var> commands, which allow you to redefine many field attributes, to delete a field's description and all its occurrences in the data, and to rename fields. For the complete syntax and description of these commands, please follow the links.</p>		This page describes the <var>[[REDEFINE command\|REDEFINE]]</var>, <var>[[DELETE command: Field\|DELETE]]</var>, and <var>[[RENAME FIELD command\|RENAME]]</var> commands, which allow you to redefine many field attributes, to delete a field's description and all its occurrences in the data, and to rename fields. For the complete syntax and description of these commands, please follow the links.</p>

	<p class="note">'''Note:''' New fields and Repeating Field Groups may may be added by the file manager at any time (although some attributes may not be assigned to these new fields (such as the [[Field design (File management)#Preallocated fields\|OCCurs attribute]] to preallocate a field) once data has been added to the file. See [[Field design (File management)\|Field design]] for more details.)</p>		<p class="note">'''Note:''' New fields and Repeating Field Groups may may be added by the file manager at any time (although some attributes may not be assigned to these new fields (such as the [[Field design (File management)#Preallocated fields (OCCURS attribute)\|OCCurs attribute]] to preallocate a field) once data has been added to the file. See [[Field design (File management)\|Field design]] for more details.)</p>

	<p>		<p>

JAL: /* Field attributes and the REDEFINE command */

2014-02-25T00:41:18Z

Field attributes and the REDEFINE command

← Older revision		Revision as of 00:41, 25 February 2014
Line 90:		Line 90:
	<tr>		<tr>
	<td rowspan=2>Data content</td>		<td rowspan=2>Data content</td>
	<td>FV or MV		<td nowrap> a) FV or MV
	<p>UP or UE</p>		<p>b) UP or UE</p>
	<p>DV</p>		<p>c) DV</p>
	<p>ONE, EXONE, or REPT</p>		<p>d) ONE, EXONE, or REPT</p>
	<p>DEF or NDEF</p>		<p>e) DEF or NDEF</p>
	</td>		</td>
	<td>Yes</td>		<td>Yes</td>
	<td>COD or FRV fields ~~only~~		<td>a) Only valid for COD or FRV fields
	<p>~~ ~~ </p>		<p>b) Not allowed with INVISIBLE fields</p>
	<p>ONE or EXONE fields only </p>		<p>c) ONE or EXONE fields only </p>
	</td>		</td>
	</tr>		</tr>

JAL: /* Redefining fields */

2014-02-24T23:52:12Z

Redefining fields

← Older revision		Revision as of 23:52, 24 February 2014
Line 34:		Line 34:
	<li><var class="term">fieldname</var> is the name of a field in the open <var class="product">Model 204</var> file.</li>		<li><var class="term">fieldname</var> is the name of a field in the open <var class="product">Model 204</var> file.</li>

	<li><var class="term">attribute</var> is one of the attributes listed in [[#~~Redefining fields~~\|~~Redefining fields~~]]. In the <var>REDEFINE</var> command, you need to specify only the attributes being changed for the field.</li>		<li><var class="term">attribute</var> is one of the attributes listed in the [[REDEFINE command#Syntax\|REDEFINE command description]]. In the <var>REDEFINE</var> command, you need to specify only the attributes being changed for the field.</li>
	</ul>		</ul>