SAF-controlled auditing using SYS1.PARMLIB

You need to define an enabling SAF facility profile as described below:

Define SAF facility profile


FILEM.PARMLIB.CICS

and ensure all ZDT/CICS users to be audited have at least read access to that facility. See the example below:

Example

User PROD1 to have SAF-rule controlled auditing using SYS1.PARMLIB.

Write this RACF® rule:


RDEF FACILITY FILEM.PARMLIB.CICS AUDIT(NONE) UACC(NONE) OWNER(ownerid)
PE FILEM.PARMLIB.CICS ACC(READ) ID(PROD1) CLASS(FACILITY)

Add member HFM3PARM to SYS1.PARMLIB (or any other library in the logical parmlib concatenation). See Defining the HFM3PARM member.

Once the above SAF rule is defined and activated, auditing for ZDT/CICS component users is controlled by the FMAUDIT parameter in the HFM3PARM member. See ZDT/CICS options specified in HFM3PARM for more information. If audit log records are to be written to SMF, the SMF record number is specified as an FMAUDIT parameter option. See FMAUDIT, and SMF_NO.

Note: ZDT/CICS does not start if a user has read access to the above facility and the HFM3PARM member does not exist in the logical parmlib concatenation.

If SAF processing is not active, or the rule is not defined, or the rule is defined and the user has no access, then no parmlib processing is performed.