Previous Topic: GSOMDOBJ  Resource Class—Secure z/OS GSOMDOBJ ObjectsNext Topic: IBMFAC Resource Class—Determine IBM Facilities Ownership


HFSSEC Resource Class—Secure HFS Files

Valid on z/OS.

Use HFSSEC to secure HFS files under CA Top Secret. For information on HFSSEC, see the Cookbook.

When used with TSS ADDTO/REMOVE, this resource class has the following format:

TSS ADDTO(acid) HFSSEC(/nnnnnn)                 
Prefix length

1 to 8 characters

Capacity of list

1 to 8 prefixes per command

Note: When you add HFSSEC, add a slash (/) unless you are using ROOT. Administratively, you can ADD and PERMIT HFSSEC without using a slash, but functionally it will not work.

When used with TSS PERMIT/REVOKE, this resource class has the following format:

TSS PERMIT(acid) HFSSEC(/nnnnnn)
                  ACCESS(READ)
Prefix length

1 to 255 characters

Note: When you permit HFSSEC, add a slash (/) unless you are using ROOT. Administratively, you can ADD and PERMIT HFSSEC without using a slash, but functionally it will not work.

This keyword is used with:

The administrator can use any of the following methods to control access to HFSSEC resources: Expiration, Facility, Program Pathing, Time/Day, and Actions.

Examples: HFSSEC resource class

This example protects the resource by assigning ownership to the Corporate Department(owning acid):

TSS ADDTO(CORPORAT) HFSSEC(ROOT)                 

The administration may now PERMIT access to users or profiles that require access.

This example removes ownership:

TSS REMOVE(CORPORAT) HFSSEC(ROOT)

This example permits users in the Technical Services Department to access BIN on Fridays only:

TSS PERMIT(TECHPROF) HFSSEC(/BIN)
                     ACCESS(READ,EXEC)
                     DAYS(FRIDAY)

This example permit users in the Technical Services Department to access HFSSEC(/BIN):

TSS PERMIT(TECHPROF) HFSSEC(/BIN)
                     ACCESS(READ,EXEC)

This example revokes access:

TSS REVOKE(TECHPROF) HFSSEC(/BIN)
                     ACCESS(READ,EXEC)