Release 14.1 of CA Common Services for z/OS now uses a //CAIRACF DD card in the CAS9 proc to define the RACF security classes needed for Datacom r14.0. If I use this DD card, will it affect the security settings for any other CA product?

Products

• CIS
• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
• COMMON PRODUCT SERVICES COMPONENT
• Common Services
• Datacom/AD
• CA ECOMETER SERVER COMPONENT FOC
• Easytrieve Report Generator for Common Services
• INFOCAI MAINTENANCE
• IPC
• UNICENTER JCLCHECK COMMON COMPONENT
• Mainframe VM Product Manager
• CHORUS SOFTWARE MANAGER
• CA ON DEMAND PORTAL
• CA Service Desk Manager - Unified Self Service
• PAM CLIENT FOR LINUX ON MAINFRAME
• MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
• GRAPHICAL MANAGEMENT INTERFACE
• WEB ADMINISTRATOR FOR TOP SECRET
• Xpertware
• Compress Data Compression for MVS
• Compress Data Compression for Fujitsu

Issue/Introduction

We are running Common Services r14.1 along with release 14.0 of CA Datacom.  RACF is our security product.  As per Datacom/DB APAR RI71276, we need to add a //CAIRACF DD statement to CAS9.   We haven't created a CAS9SAFC User Exit and don't have the prebuilt exit CAS9SAFC in our CAW0LOAD loadlib.   

If i add the CAIRACF DD statement to CAS9, will this affect other the security settings for any other of the CA products installed on our system?  If so, what preventive action do we need to take? 

 

 

Environment

CA Common Services for z/OS r14.1, Datacom/DB release 14.0 using IBM RACF security.

Cause

Release 14.1 of CA Common Services for z/OS changed the method of defining RACF Security Classes for the various CA mainframe products that may require them.   Datacom/DB is one of them and documentation apar RI71276 details the RACF Security Class definitions necessary for Datacom/DB r14.0.  

Resolution

CA Common Services Version 14.1 modified the method by which CAS9SAFC RACF external security resource class definitions are added or changed.

Prior to Version 14.1, a CAS9SAFC source module had to be updated, assembled and link edited if additions or changes were needed. Beginning with Version 14.1, a //CAIRACF DD statement included in the CAS9 proc now points to control cards that define the necessary RACF security classes.  The RACF security class table is built dynamically when CAIRIM reads and processes these definitions.   

 

Additional Information

Please refer to the following documentation for details about the changes to the method of defining the necessary RACF security classes: 

• The CA Common Services r14.1 Release Notes
• The CA Common Services r14.1 Documentation wiki describing the changes to the customization required for RACF sites