Why does CA HealthChecker start when it is not installed?


Article ID: 16795


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 Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component 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 CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu


I recently upgraded CA Common Services to 14.1 on one of our test systems, which included starting
the new CAMASTER address space, all of which worked as expected.

We are now rolling the update out to other systems, and on one of them (so far) I can see a S806 abend for CAHCHECK during the IPL. Why is CAMASTER attempting to start CAHCHECK on this system and not on others?
We do not have CAHCHECK installed.


Why does CA HealthChecker start when it is not installed?


CA Common Services 14.1 - z/OS Supported Releases -


On the system where you have CAMASTER starting CA Health Checker, I am wondering if you have Health Checker start coded in another member, for exemple in CAIMST20:

So I assume that you have:

START=YES /* Do not start at IPL */

on the lpar where CA Health Checker is started.

Here is the link to this information:


CAIMST20 Example Parameter Statements:
To override the CAHCHECK component address space so it does not start automatically at IPL time, specify:

START=NO /* Do not start at IPL */





Additional Information

You can refer to the following link: