Resources › SERVAUTH Resource Class—Secure TCP/IP Resources

SERVAUTH Resource Class—Secure TCP/IP Resources

Valid on z/OS.

Use SERVAUTH to protect TCP/IP resources from unauthorized access.

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

TSS ADDTO(acid) SERVAUTH(resource)

Prefix length

One to eight characters

Capacity of list

One to fives prefixes per TSS command.

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

TSS PERMIT(acid) SERVAUTH(resource)

Prefix length

One to 64 characters

Capacity of list

One to five prefixes per TSS command.

This keyword is used with:

• The commands CREATE, ADDTO, REMOVE, PERMIT, REVOKE, ADMIN, DEADMIN, WHOOWNS, and WHOHAS
• The SERVAUTH ACID types User, Profile, Department, Division, Zone, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS ADD/REMOVE
• The SERVAUTH ACID types User, Profile, DCA, VCA, ZCA, LSCA, SCA, and MSCA when used with TSS PERMIT/REVOKE
• SERVAUTH(OWN) authority via the TSS ADMIN function to ADD or REMOVE ownership of SERVAUTH resources from ACIDs
• SERVAUTH(XAUTH) authority via the TSS ADMIN function to permit or revoke access to SERVAUTH resources

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

Examples: SERVAUTH resource class

This example protects resources by using CA Top Secret, by assigning ownership to the Corporate Department (owning acid):

TSS ADDTO(CORPORAT) SERVAUTH(EZB.)

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

This example removes ownership:

TSS REMOVE(CORPORAT) SERAUTH(EZB.)

This example permits users in the Technical Services Department to access TCP/IP stack:

TSS PERMIT(acid) SERAUTH(EZB.STACKACCESS.)
                 ACCESS(READ)

This example revokes access:

TSS REVOKE(acid) SERVAUTH(EZB.STACKACCESS.)