Error message implementing sysview performance manager for db2 version 19

book

Article ID: 75128

calendar_today

Updated On:

Products

CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS

Issue/Introduction

Error: hzs0002e 056 customization error in idb2 interface, dbghc021e= sysvie db2 collect = definitions need customizing, data sharing inconsistanct, dbghc001e = dispatching priority may result in lost data. Issue: Client needs assistance with removing old datasets from application. She's getting message that may cause issue in production and needs assistance setting prioirties for dispactch base on her system.

Environment

Release:
Component: CIDB

Resolution

The HZS0420E 'THIS CHECK HAD A DATE CONFLICT. ' relates to the IBM Health Checker which indicates that the policy statement date is older than the date that the check was added indicating that that the policy statement may have been written against an older version of the check and may no longer be appropriate. To alleviate the HZS0420E errors concerning the 'Date Conflict', you can modify the policy statements in your SYSx.PARMLIB(HZSPRMxx) member to use symbolics instead of hard coded date values. Example: DATE(&YR4&LMON&LDAY) Reason(Ignore DBGHC001E CA Insight may result in lost data) Instead of a hardcoded date like: Date(20150815) Reason(Ignore DBGHC001E CA Insight may result in lost data) - With the symbolic there is no need to maintain the date in the future.