When starting up CA-1 R12.6 at IPL, I see the following messages: TMSHCS03 Running CA 1 health checks (CA_1,CA1_Vrfy*) and CAHC101I Function Code: 10 Return Code: 60 Reason Code: 3073 Why are these messages occurring? Â

book

Article ID: 6944

calendar_today

Updated On:

Products

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

Issue/Introduction

CA-1 is started at IPL.  I see the following messages written to the syslog: 

TMSHCS03 Running CA 1 health checks (CA_1,CA1_Vrfy*)

CAHC101I Function Code: 10 Return Code: 60 Reason Code: 3073

 

 

Cause

TMSHCS03 - Running CA 1 health checks (CA_1,CA1 Vrfy*).  
This message is issued because at startup, TMSINIT may have changed parameters that the health checks monitor so all CA 1 health checks whose names begin with CA1_Vrfy will be run to examine possible changes made to the parameters.

There are various reasons for receiving the CAHC101I Function Code: 10 Return Code: 60 Reason Code: 3073
message for the CA-1 Health Checks.

  • The CA Common Services Health Checker address space (CAHCHECK) is not active
  • The IBM Health Checker address space is not active
  • The CA-1 CTS address space is not active 

The CAHC101I message is not exclusive to the health checks for CA-1.  It can possibly be issued for the health checks of other CA Products as well.   

Environment

Executing the CA-1 Health Checks with CA Common Services for z/OS

Resolution

The Health Checker component of CA Common Services for z/OS (HCKCCS) was introduced as an enhancement to CCS390 release 12.0 and was incorporated into the subsequent v14.0 and r14.1 releases.  Although it is currently an optional component, the CAHCHECK address space is utilized to host the CA Product Health Checks.  The IBM Health Checker is required for successful startup of this equivalent CA component.  If CAHCHECK is not available, the CA-1 CTS task is a requirement for CA-1 as it includes a CTSHCK subtask which provides the health checks for CA-1.   

 

 

Additional Information

Refer to the CA-1 message TMSHCS03 and the Common Services Health Checker message CAHC101I found in docops.ca.com.