Why does CA HealthChecker start when it is not installed?

Products

• COMMON SERVICES FOR Z/OS
• 90S SERVICES
• Common Services

Issue/Introduction

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?

Environment

CA Common Services 14.1 - z/OS Supported Releases -

Resolution

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:

COMPONENT(CAHCHECK), /* CAHCHECK */
START=YES /* Do not start at IPL */

on the lpar where CA Health Checker is started.

Here is the link to this information:

https://docops.ca.com/ca-common-services-for-z-os/14-1/en/component-reference/address-spaces/camaster-address-space/optional-caimst20-logical-parmlib-concatenation-member

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

COMPONENT(CAHCHECK), /* CAHCHECK */
START=NO /* Do not start at IPL */

 

 

 

 

Additional Information

You can refer to the following link:

https://docops.ca.com/ca-common-services-for-z-os/14-1/en/component-reference/address-spaces