Where can one find information on ACF2 health check setup.
Release: 16.0
Component: ACF2 for Z/OS
- WRITE access to PRODSYS.HZSPDATA.
- READ access to SYS1.PARMLIB.
If using a log stream:
- write a resource rule for the Resource TYPE mapped to the LOGSTRM Resource Class (as delivered it is SAF - check ACF SHOW CLASMAP output) - and give the Logonid SERVICE(UPDATE) access to the logstreamname, e.g.:
$KEY(logstreamname) TYPE(saf)
UID(uidmask) SERVICE(UPDATE) ALLOW
- if the resource type is resident (check ACF SHOW RESIDENT output) issue command F ACF2,REBUILD(saf).
- write a resource rule for the Resource TYPE mapped to the FACILITY Resource Class (as delivered it is FAC - check ACF SHOW CLASMAP output) and give the HZSPRINT utility Logonid SERVICE(READ) access to the logstreamname, e.g.:
$KEY(logstreamname) TYPE(fac)
UID(uidmask) SERVICE(READ) ALLOW
- if the resource type is resident (check ACF SHOW RESIDENT output) issue command F ACF2,REBUILD(fac).
RACF ACF2 Resource Rule ----- --------------------- READ READ UPDATE UPDATE ALTER ADD CONTROL DELETE EXECUTE EXECUTE
Note that RACF attributes are hierarchical so, for example, UPDATE includes READ access; in ACF2 each attribute must be specified, e.g. SERVICE(READ,UPDATE). If no SERVICE keyword is included in the resource rule, all accesses are allowed.
A very basic rule that would allow all users access to all HZS resources would be:
$KEY(HZS) TYPE(XFC)
- UID(*) ALLOW
Changing ALLOW to LOG would log to SMF and ALLOW all validations.
For details on Resource rules, the GSO INFODIR and the MODIFY ACF2 commands see the CA ACF2 for z/OS Administration Guide.