Defining RACF profiles

You define three types of profiles:

1. Data Set Profiles

   Define data set profiles for all data sets used by HCD.

2. OPERCMDS Class Profile:

   Define the profile MVS.ACTIVATE to invoke the dynamic reconfiguration function under HCD, to use the MVS operator command ACTIVATE from an MVS console, or to use the HCD I/O Autoconfiguration functionality. For a description of the command syntax, see z/OS MVS System Commandsz/OS MVS System Commands. For a description of I/O Autoconfiguration, see How to work with I/O Autoconfiguration.

   If you issue the ACTIVATE command, the I/O supervisor calls jobname IEASYSAS stepname IOSAS to assist in the activate procedure. IOSAS requires read access to the IODF data sets. Because the default entry for IOSAS in the Program Properties Table (PPT) is PASS, RACF checking occurs. ICH408I is the result of an ACTIVATE IODF=XX command. To ensure the successful completion of the activate process, you have to choose one of the following alternatives:

   • Place the IOSAS task into the RACF started task table (ICHRIN03) and indicate that the user is authorized.
   • Define the IODF data sets to RACF with UACC=READ.
   • Add IOSAS as an entry in the Started Procedures Table with a valid user ID. This user ID must have read access to the SYS1.NUCLEUS and the IODF data sets.

   The ACTIVATE command needs UPDATE access, regardless whether the TEST option is specified or not.

   You also have to define the profile MVS.DISPLAY.IOS with read access if you wish to work from the sysplex member list to view the active configuration status or to process a CONFIGxx member.

3. FACILITY Class Profiles:

   Define the following profiles:

   • CBD.CPC.IPLPARM to query and update the IPLADDR and IPLPARM attribute values of the last IPL, and to be used for next IPL.
   • CBD.CPC.IOCDS to query and update IOCDS control information.

   To enable users to work with CPC images (see Activate a configuration HMC-wide), you need to define the following profile:

   • HWI.TARGET.network.cpcname.* - using the BCPii community name specified with APPLDATA('community_name'). This community name must be defined on the support element of each CPC that is queried.

   See also Access to HWI.* profiles.