Getting CA ACF2 violations after writing rule changes for HFSSEC resource
search cancel

Getting CA ACF2 violations after writing rule changes for HFSSEC resource

book

Article ID: 137384

calendar_today

Updated On:

Products

ACF2 ACF2 - DB2 Option ACF2 for zVM ACF2 - z/OS ACF2 - MISC

Issue/Introduction

New Users are added to resource rule for HFSSEC validation.

The validation is failing and I cannot understand why.

Rules were checked and looked to be correct





Environment

Release : 16.0

Component : CA ACF2 for z/OS

Resolution

Whilst reviewing the violation it is noted that the resource name in ACFRPTRV is in mixed case.

This is unusual because the CONTROL(GSO) CLASMAP record for class HFSSEC normally has the following

 ********   HFSSEC      HFS    39                                         

this shows that mixed case resource names will be upper cased for validation however, in this case the CONTROL(GSO) clasmap record had been modified to validate the rules in mixed case format

by adding MIXED to the clasmap.

********   HFSSEC      HFS    39               LOG    MIX      EXT 

Any reference in the rule to mixed case resource names must be entered in mixed case.  

Additional Information

Section "SAF Resource Classes (CLASMAP)"


MIXED|

NOMIXED 

Indicates whether 

CA ACF2 

 accepts all input of resource names as mixed case. When MIXED is chosen, the inserted CLASMAP must be made active via the ACF2 REFRESH command before any subsequent administration commands can be issued for this resource class.