Questions about Healthcheck changes and additions
search cancel

Questions about Healthcheck changes and additions

book

Article ID: 97735

calendar_today

Updated On:

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 currently reviewing our Healthcheck environment, amending monitoring, thresholds, escalations for the various checks in place. 

From a CA perspective, how are CHANGES to the numerous CA HC's communicated to the userbase, is it via DOC HOLDDATA or will be covered by ACTION HOLDS?

In our shop ACTION holds get reviewed but due to the number of DOC HOLDS in a maint drop DOC HOLDS often only get a cursory skim read so any healthcheck information could be missed. 

For NEW healthchecks, again is this disseminated via DOC or ACTION HOLDS or is it up to the site so see what new HC's have been registered following a maintenance drop? 

 


Do you have any CA specific guidance and best practice for healthchecks and reviewing updates and changes?
 

Environment

CA Common Services 14.1 - z/OS supported releases - 

Resolution

Individual products deliver health checks, not CA Common Services. 

CA Health check is only the service that we deliver to allow products to interface with the IBM Health check facility HZSPROC. 

Any information about health checks would need to be delivered by the individual product.