How to validate/test CCS applied maintenance


Article ID: 198267


Updated On:


CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA LDAP Server for z/OS CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware MF - MISC OLD CODES SERVICE ASSURE Generic Uniservice for CICS Generic Uniservice II CA Output Management Web Viewer


Questions about CA COMMON SERVICES (PRE and POST maintenance)

1) How do I test CAS9 initialization given it is the only started at System IPL?

2) Is there other testing I many need to do to ensure I won't have fallout from the CCS maintenance?



IVP to confirm BROADCOM Products

Is there a method to test Common Services after maintenance


Release : 15.0



1) There are NO IVP jobs for Common Services.

2) The quickest way to confirm the proper execution of CAIRIM is to check the output of CAS9 procedure at IPL time.  

  • Verify that the KEYS were accepted
  • Ensure that the products started by CAIRIM have all initialized successfully  

Common Services also offers 3 Utilities to verify the initialization of resources which would need to be executed prior to the maintenance activation (for comparison of the output), then after the IPL   

  • CAIRIMU displays the status of all modules initialized by CAIRIM. 
  • CAISMFU displays the status of the SMF exits installed by CAIRIM 
  • CAISUBU displays the status of the subsystems installed by CAIRIM. 

Additional Information

Refer to the Common Services r15.0 Documentation regarding the above topics: