Previous PageTable Of ContentsNext Page

    ACCEPT SFS Object Rule


.

ACCEPT
--------

-

Requestor Action SFSObject [(ACIGROUP MIXED
-------------------------------------------------------

    Requestor -{[USER] ReqUser, ACIGROUP ReqGroup}

    Action ---- {READ, WRITE, CO-OWNER}

    SFSObject - [fn ft] fp:fs.[dir1[.dir2[...dir8]]][.]

    -


Purpose

The ACCEPT SFS Object Rule allows Action by Requestor to SFSObject

Parameters

Requestor:

    USER Userid

Pattern matched requesting userid. This is the user(s) who will be affected by the rule. The keyword USER is optional and may be omitted.

   

    ACIGROUP Groupid

Pattern matched group of users who will be affected by the rule. The rule applies to all members of the acigroup(s) Groupid.


Action:

    READ

Allows "READ" access by Requestor to SFSObject.

   

    WRITE

Allows "WRITE" access by Requestor to SFSObject.

   

    CO-OWNER

Allows "CO-OWNER" access by Requestor to the filespace specified in SFSObject. The SFS Object must consist of * for the filepool name and a filespace. Since Co-Ownership applies to a filespace in all filepools, other tokens in SFS Object are not allowed. The ACIGROUP option indicating all filespaces owned by members of the ACIGROUP is allowed.


SFSObject:
[fn ft] fp:fs.[dir1[.dir2[...dir8]]][.]

    Fn

1 to 8 character pattern matched file name. File type is required if file name is specified.

    Ft

1 to 8 character pattern matched file type. File name is required if file type is specified.

    Fp

1 to 8 character pattern matched file pool name.

    Fs

1 to 8 character pattern matched file space name.

    Dir1...dir8

Each directory specified is a 1 to 16 character pattern matched directory name.


Options

    ACIGROUP

Indicates that the fs specified in Object is an acigroup, not a file space. fs in Object indicates all filespaces owned by members of the matching acigroup.

   

    MIXED

Indicates that the filename and filetype specified in the SFS Object contain mixed case characters and should not be upper cased by SafeSFS.



Usage Notes

  1. fp:fs. in the SFS object, is required. The period following the filespace is also required. All other tokens of the SFS object are optional. If directories are specified, they must be preceded by a period. The period following the last directory is optional. Trailing pattern matching may be used by specifying an *.



Examples
  1. ACCEPT JIM READ *:JOE.
    This rule allows JIM to read file space JOE and all objects in it. The rule applies to all file pools served by the SafeSFS server because the filepool is an *.


  2. ACCEPT JIM READ *:JOE.PROGRAMS
    This rule allows JIM to read the PROGRAMS directory in the JOE file space and all objects in the directory. The rule applies to all file pools.


  3. ACCEPT * READ * EXEC *:JOE.PROGRAMS
    This rule allows all users to read all files with a file type of EXEC, in the JOE file space PROGRAMS directory in all file pools.


  4. ACCEPT JIM READ * ASSEMBLE TFP:JOE.PROGRAMS
    This rule allows JIM to read all files with a file type of ASSEMBLE in the JOE file space PROGRAMS directory. The rule applies to the TFP file pool only.


  5. ACCEPT BILL READ *:JOHN.
    REJECT BILL READ *:JOHN.*
    The two rules above, allow BILL to read all files in the JOHN file space in all file pools, but prevent BILL from reading any of the directories in the JOHN file space.


Previous PageTable Of ContentsNext Page