ELowell at 22:54, 12 July 2016

2016-07-12T22:54:42Z

← Older revision		Revision as of 22:54, 12 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:04, 11 July 2016

2016-07-11T22:04:18Z

← Older revision		Revision as of 22:04, 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 IFFLS call (FIELD LEVEL SECURITY) checks security access level to a specified field, or to all fields, in a file or group on the..."

2016-07-07T19:23:20Z

Created page with " ==Summary== <dl> <dt>Description</dt> <dd>The IFFLS call (FIELD LEVEL SECURITY) checks security access level to a specified field, or to all fields, in a file or group on the..."

New page

==Summary==
<dl>
<dt>Description</dt>
<dd>The IFFLS call (FIELD LEVEL SECURITY) checks security access level to a specified field, or to all fields, in a file or group on the current thread.</dd>
<dt>Thread type</dt>
<dd>multiple cursor IFSTRT, single cursor IFSTRT</dd>
<dt>IFCALL function number</dt>
<dd>61</dd>
</dl>

==Syntax==
IFFLS(RETCODE,FIELD_NAME,ACCESS_SPEC,FILE_IND)
<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 a required output parameter. The code is a binary integer value.</td>
</tr>
<tr>
<td>FIELD_NAME</td>
<td>[I,c,o] The field name is an optional input parameter which specifies the name of the field or identifies a field name variable for a field whose security access level is to be checked.
Note: If the field name is not specified, IFFLS defaults to checking all of the fields in the indicated file or group. In this case, Model 204 returns a completion code of 0 only if the thread has the requested access to every field. Use IFFLS without specifying a field name with caution; since this requires that Model 204 examine every field, it can slow performance.
</td>
</tr>
<tr>
<td>ACCESS_SPEC</td>
<td>[I,s,o] The access specification is an optional input parameter which summarizes the needed field access. Specify a short character string which contains any of the following character codes:

S = SELECT 
R = READ 
U = UPDATE 
A = ADD 
Note: If you do not specify the access codes, the specification defaults to a value of SRUA, for all privileges.
</td>
</tr>
<tr>
<td>FILE_IND</td>
<td>[I,s,o] The file indicator is an optional input parameter which specifies the file or group context for the access check. If you do not specify the file indicator, IFFLS uses the context established by the IFOPEN call. You can specify the file indicator in one of the following ways on a single cursor IFSTRT thread:
<ul>
<li>If the access is to be checked for a particular file in the group, specify that file name.</li>
<li>If the access is to be checked for the file containing the current record, specify the $CURFILE string.</li>
<li>To indicate the group update file, specify the $UPDATE string.</li>
</ul>

In group context, IFFLS returns a completion code of 0 if there is a set of files in the group for which the access would be allowed.

On a multiple cursor IFSTRT thread, you can specify any file or group using the following format: 
filename 
Note: On a multiple cursor IFSTRT thread, $UPDATE and $CURFILE are illegal.
</td>
</tr>
</table>

==Usage notes==

Use the IFFLS call to avoid or diagnose errors that occur because of field level security violations. You can use the IFFLS call on any type of IFSTRT thread. 

==Completion return code (RETCODE)==

If the IFFLS call is unsuccessful, Model 204 returns an error code of 4 if any one of the following error conditions occurs:
<ul>
<li>The indicated access (ACCESS_SPEC) is not allowed.</li>
<li>The access string (ACCESS_SPEC) is invalid.</li>
<li>The field name (FIELD_NAME) is not defined.</li>
<li>No file or group is open.</li>
<li>The file indicator (FILE_IND) is invalid.</li>
</ul>

==Coding example (COBOL)==
WORKING-STORAGE SECTION.
01 ARGS-FOR-CALL.
05 RETCODE PIC 9(5) COMP SYNC.
05 FIELDNAME PIC X(7) VALUE "SALARY;".
05 ACCESS PIC X(2) VALUE "U;".
.
.
.
PROCEDURE DIVISION.
.
.
.
CALL "IFFLS" USING RETCODE, FIELDNAME, ACCESS.

[[Category: HLI functions]]

IFFLS (HLI function) - Revision history

ELowell at 22:54, 12 July 2016

ELowell at 22:04, 11 July 2016

ELowell: Created page with " ==Summary== Description The IFFLS call (FIELD LEVEL SECURITY) checks security access level to a specified field, or to all fields, in a file or group on the..."

ELowell: Created page with " ==Summary==

Description

The IFFLS call (FIELD LEVEL SECURITY) checks security access level to a specified field, or to all fields, in a file or group on the..."