z/OS MVS Setting Up a Sysplex
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Authorizing coupling facility requests

z/OS MVS Setting Up a Sysplex
SA23-1399-00

As documented by the subsystem or application using a coupling facility structure, the security administrator might have to define security profiles for certain structures. If the z/OS® Security Server, which includes RACF®, or another security product is installed, the administrator can define profiles that control the use of the structure in the coupling facility.

The following steps describe how the RACF security administrator can define RACF profiles to control the use of structures:

  1. Define resource profile IXLSTR.structure-name in the FACILITY class.
  2. Specify the users who have access to the structure using the RACF PERMIT command.
  3. Make sure the FACILITY class is active, and generic profile checking is in effect. If in-storage profiles are maintained for the FACILITY class, refresh them.
For example, if an installation wants to permit an application with an identifier of SUBSYS1 to issue the IXLCONN macro for structure-name CACHE1, the security administrator can use the following commands:
RDEFINE FACILITY IXLSTR.CACHE1 UACC(NONE)

PERMIT IXLSTR.CACHE1 CLASS(FACILITY) ID(SUBSYS1) ACCESS(ALTER)

SETROPTS CLASSACT(FACILITY)

You can specify RACF userids or RACF groupids on the ID keyword of the PERMIT command. If RACF profiles are not defined, the default allows any authorized user or program (supervisor state and PKM allowing key 0-7) to issue coupling facility macros for the structure.

For information about RACF, see z/OS Security Server RACF Security Administrator's Guide.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014