After applying maintenance for Common Services for z/OS, we get HZS0420E Health Check error.

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

After applying maintenance on my Test LPAR, we are getting the following errors during IPL:

HZS0420E 1 CHECKS HAVE BEEN FOUND FOR WHICH AT LEAST ONE MATCHING
POLICY STATEMENT HAD A CONFLICT WITH THE CHECK VALUES.
THE POLICY STATEMENTS WERE NOT APPLIED TO THOSE CHECKS.
THE FIRST CASE IS
CHECK(CA_CCS,CCS_ENF_SCREEN_VALIDITY),
MATCHED BY POLICY STATEMENT DEL2
THIS CHECK HAD A DATE CONFLICT.

Environment

Release: CA90SV00200-14.1-Common Services-for z/OS
Component:

Cause

Maintenance that updates LMOD CAS9MNGR will generally update the assemble date for this module. Because this module is responsible for adding the CA-ENF health check during the ADD CHECK process, the date specified on the related ENF health check policy statement may become "outdated".

The IBM Health Check services are the services doing the date comparisons (not CAHCHECK).  The two dates being compared are the DATE= in the HZSPRMxx parmlib member and the DATE= parameter on the HZSADDCK macro.

In the case of “CHECK(CA_CCS,CCS_ENF_SCREEN_VALIDITY”, the date used on the HZSADDCK macro is the assemble date of the CAS9MNGR module.

If the assembly date on the HZSADDCK  is more recent than Date specified on the policy statement in HZSPRMxx, you get the “HZS0420E” message.

Resolution

Update the related POLICY statement in HZSPRMxx to specify the current date, or a date more recent than the assembly date for LMOD CAS9MNGR.

After the DATE has been updated and saved, issue the following commands:

1. F HZSPROC,SET,PARMLIB=(xx) where xx was the specific suffix for the HZSPRM parmlib member above
2. F HZSPROC,REFRESH,CHECK=(*,*) or refresh the single check causing the issue