IFRFLD (HLI function) - Revision history

JAL: link repair

2017-04-07T21:34:19Z

link repair

← Older revision		Revision as of 21:34, 7 April 2017
Line 64:		Line 64:
	<p class="note"><b>Note:</b> The file context can change on a multiple cursor thread and, if the file specification parameter (FILE_SPEC) is omitted, IFRFLD redefines the field for the default file on the thread.</p>		<p class="note"><b>Note:</b> The file context can change on a multiple cursor thread and, if the file specification parameter (FILE_SPEC) is omitted, IFRFLD redefines the field for the default file on the thread.</p>
	<p>		<p>
	If the field being redefined has a security level, the Model 204 file manager must have field level security (FLS) access privileges. Note that changing a field's security level to 0 desecures the field. For information about field security, see [[~~Security~~#Field-level security\|Field-level security]].</p>		If the field being redefined has a security level, the Model 204 file manager must have field level security (FLS) access privileges. Note that changing a field's security level to 0 desecures the field. For information about field security, see [[Model 204 security features#Field-level security\|Field-level security]].</p>
	<p>		<p>
	Note also that IFRFLD follows the same basic rules for specifying field attribute definitions as the Model 204 <var>[[REDEFINE command\|REDEFINE FIELD]]</var> command.</p>		Note also that IFRFLD follows the same basic rules for specifying field attribute definitions as the Model 204 <var>[[REDEFINE command\|REDEFINE FIELD]]</var> command.</p>

JAL: link repair

2016-08-08T21:45:03Z

link repair

← Older revision		Revision as of 21:45, 8 August 2016
Line 66:		Line 66:
	If the field being redefined has a security level, the Model 204 file manager must have field level security (FLS) access privileges. Note that changing a field's security level to 0 desecures the field. For information about field security, see [[Security#Field-level security\|Field-level security]].</p>		If the field being redefined has a security level, the Model 204 file manager must have field level security (FLS) access privileges. Note that changing a field's security level to 0 desecures the field. For information about field security, see [[Security#Field-level security\|Field-level security]].</p>
	<p>		<p>
	Note also that IFRFLD follows the same basic rules for specifying field attribute definitions as the Model 204 <var>[[REDEFINE ~~FIELD~~ command\|REDEFINE FIELD]]</var> command.</p>		Note also that IFRFLD follows the same basic rules for specifying field attribute definitions as the Model 204 <var>[[REDEFINE command\|REDEFINE FIELD]]</var> command.</p>

	==Coding example (COBOL)==		==Coding example (COBOL)==

ELowell at 19:35, 13 July 2016

2016-07-13T19:35:11Z

← Older revision		Revision as of 19:35, 13 July 2016
Line 1:		Line 1:
	The conventions used on this page are described in [[HLI: Function ~~call list~~#Function call notation conventions\|Function call notation conventions]].		The conventions used on this page are described in [[HLI: Function summary#Function call notation conventions\|Function call notation conventions]].

	==Summary==		==Summary==

ELowell at 22:53, 11 July 2016

2016-07-11T22:53:44Z

← Older revision		Revision as of 22:53, 11 July 2016
Line 1:		Line 1:
			The conventions used on this page are described in [[HLI: Function call list#Function call notation conventions\|Function call notation conventions]].

	==Summary==		==Summary==

ELowell: Created page with " ==Summary==

Description

The IFRFLD call (REDEFINE FIELD) redefines one or more fields that have been previously defined for a Model 204 file. IFRFLD require..."

2016-07-08T18:57:39Z

Created page with " ==Summary== <dl> <dt>Description</dt> <dd>The IFRFLD call (REDEFINE FIELD) redefines one or more fields that have been previously defined for a Model 204 file. IFRFLD require..."

New page

==Summary==
<dl>
<dt>Description</dt>
<dd>The IFRFLD call (REDEFINE FIELD) redefines one or more fields that have been previously defined for a Model 204 file. IFRFLD requires Model 204 file manager privileges.</dd>
<dt>Thread type</dt>
<dd>multiple cursor IFSTRT, single cursor IFSTRT</dd>
<dt>IFCALL function number</dt>
<dd>59</dd>
</dl>

==Syntax==
IFRFLD(RETCODE,FIELD_DESC,FILE_SPEC)

<dl>
<dt>Compile-only form</dt>
<dd>Not available</dd>
<dt>Execute-only form</dt>
<dd>Not available</dd>
</dl>

Specify the parameters in the syntax order shown above. 
<table>
<tr class="head">
<th>Parameter</th>
<th>Description</th>
</tr>
<tr>
<td>RETCODE</td>
<td>[O,i,r] The Model 204 return code is the required first parameter. The code is a binary integer value.</td>
</tr>
<tr>
<td>FIELD_DESC</td>
<td>[I,c,r] The field description is a required input parameter that specifies the name of the field to be redefined and a list of its new attributes. You may specify more than one field to be redefined. Specify the field description as a character string using the following format:
fieldname (attribute ...)
[fieldname (attribute ...)];

where:

<var class="term">fieldname</var> is required and specifies the name of the Model 204 field that is being redefined. Specify the name as a character string, up to 255 characters in length. 

<var class="term">attribute</var> is required and specifies a particular characteristic that controls how the field is used, stored, or accessed. You may specify more than one attribute, separating each by a comma or a blank. Specify only the attributes to be changed.

The attributes that can be specified using the IFRFLD call are identical to those that are used with the Model 204 <var>[[REDEFINE command|REDEFINE]]</var> command.
</td>
</tr>
<tr>
<td>FILE_SPEC</td>
<td>[I,s,o] The file specification is an optional input parameter for use only with a multiple cursor IFSTRT thread for specifying the name of the Model 204 file that contains the field to be redefined. Specify the name of the file as a short character string variable using the following format:
IN [FILE] <var class="term">filename</var>

The specified file must be open on the thread; otherwise, the call is unsuccessful and Model 204 returns a completion code of 4.
</td>
</tr>
</table>

==Usage notes==

Use the IFRFLD call to redefine a previously defined field in an open Model 204 file. Using the IFRFLD call allows a field definition to be altered without requiring that the file be reinitialized or reloaded. The IFRFLD call is valid only in file context, not for a group. The IFRFLD call is valid on all types of IFSTRT threads.

When FOPT=X'10' and the date/time stamp feature is installed, the IFRFLD function is supported for DTS files.

Note: The file context can change on a multiple cursor thread and, if the file specification parameter (FILE_SPEC) is omitted, IFRFLD redefines the field for the default file on the thread.

If the field being redefined has a security level, the Model 204 file manager must have field level security (FLS) access privileges. Note that changing a field's security level to 0 desecures the field. For information about field security, see [[Security#Field-level security|Field-level security]].

Note also that IFRFLD follows the same basic rules for specifying field attribute definitions as the Model 204 <var>[[REDEFINE FIELD command|REDEFINE FIELD]]</var> command.

==Coding example (COBOL)==
WORKING-STORAGE SECTION.
01 CALL-ARGS.
05 RETCODE PIC 9(5) COMP SYNC.
05 MODIFY PIC X(20) VALUE 'FIELDA (UP,LEVEL 0);'.
.
.
.
PROCEDURE DIVISION.
.
.
.
CALL "IFRFLD" USING RETCODE, MODIFY.

[[Category: HLI functions]]

IFRFLD (HLI function) - Revision history

JAL: link repair

JAL: link repair

ELowell at 19:35, 13 July 2016

ELowell at 22:53, 11 July 2016

ELowell: Created page with " ==Summary== Description The IFRFLD call (REDEFINE FIELD) redefines one or more fields that have been previously defined for a Model 204 file. IFRFLD require..."

ELowell: Created page with " ==Summary==

Description

The IFRFLD call (REDEFINE FIELD) redefines one or more fields that have been previously defined for a Model 204 file. IFRFLD require..."