I installed a product that utilizes a new resource class, but all of the validations are being done with the TYPE code of SAF, instead of the first three characters of the resource class for the rule type? Why?
The CA-ACF2 GSO CLASMAP record translates eight-character resource classes into three-character CA-ACF2 resource type codes. Some sites may have a catchall CLASMAP with a masked resource name (all asterisk's "*") so all undefined resource class will use the type code SAF, instead of the first three character of the resource class name. If there is no "catchall" CLASMAP record, then undefined resource classes will by default use the first three characters of the resource class.
When a resource validation is performed ACF2 searches the CLASMAP table for a matching entry. This table includes site defined and internally defined CLASMAP records that translate eight-character resource classes into three-byte CA-ACF2 for z/OS resource type codes. The CLASMAP RESOURCE name specifies the explicit eight-character resource class or a masked resource name.
A catch-all record is defined as RESOURCE(********) RSRCTYPE(SAF) and would look like the following at the end of a ACF SHOW CLASMAP display:
MUSASS RESOURCE TYPE ENTITY PROFINT LOG MIXED EXTERNAL POSIT ID CLASS CODE LENGTH VALUE ======== ======== === ====== ======= === ===== ======== ===== ..... ******** ******** SAF 39 EXT
If there is no such catchall record, then ACF2 uses the first three characters of the resource name as the type code.
Details on the ACF2 GSO CLASMAP records can be found in the CA-ACF2 Administrator Guide in the chapter on "Understanding SAF."