What setup is required for Hardware Configuration Manager (HCM) Security with CA ACF2?

Products

• ACF2
• ACF2 - DB2 Option
• ACF2 for zVM
• ACF2 - z/OS
• ACF2 - MISC
• PanApt
• PanAudit

Issue/Introduction

What setup is required for Hardware Configuration Manager (HCM) Security with CA ACF2?

 

 

 

Environment

Release:
Component: ACF2MS

Resolution

The Hardware Configuration Manager (HCM) is a programmable workstation based client/server interface to HCD (Hardware Configuration Definition) that combines the logical and physical aspects of hardware configuration management.

The HCM Dispatcher runs as a started task. Any logonid defined for the HCM Dispatcher started task needs to have permission to use UNIX System Services. You can set up a logonid for HCM as follows:

SET LID
INSERT logonid NAME(HCM dispatcher logonid) STC GROUP(stcgroup) HOME(/) OMVSPGM(/bin/sh) UID(nnnn)

If the group assigned to the HCM started task is not already defined, you need to create a group profile for it. In this example the stcgroup is assigned a GID of 20. The following is an example of the necessary commands:

SET PROFILE(GROUP) DIV(OMVS)
INSERT stcgroup GID(20)

Once you create the required records, you have to tell CA-ACF2 about the new records before they go into effect. To do this, issue the following commands:

F ACF2,REBUILD(GRP),CLASS(P)
F ACF2,REBUILD(USR),CLASS(P)
F ACF2,OMVS

In addition to the USS setup, the HCM started task automatically accesses SYS1.NUCLEUS, so any user of HCM must have read access permission for SYS1.NUCLEUS.