DFHHC0801W messages seen after upgrade to CICS/TS 6.1 in an ACF2 environment
search cancel

DFHHC0801W messages seen after upgrade to CICS/TS 6.1 in an ACF2 environment

book

Article ID: 262540

calendar_today

Updated On:

Products

ACF2 - z/OS ACF2 ACF2 - MISC

Issue/Introduction

After upgrading to CICS/TS 6.1 the following messages appear every 30 minutes in the CICS JESMSGLG:

+DFHHC0801W 03/16/2023 06:21:54 CICSXXXX Transaction CESF does not invoke program DFHSFP.
+DFHHC0801W 03/16/2023 06:21:54 CICSXXXX Transaction CESL does not invoke program DFHSNP.
+DFHHC0801W 03/16/2023 06:21:54 CICSXXXX Transaction CESN does not invoke program DFHSNP.
+DFHHC0801W 03/16/2023 06:21:54 CICSXXXX Transaction CSGM does not invoke program DFHGMM.

It was identified that the messages are issued from a new z/OS Health Check CICS_CAT3_CONFIGURATION. 
Since ACF2 is active, the transaction definitions for CESF/CESL/CESN/CSGM are overridden to point to ACF2 programs.

How can these messages be suppressed?

Environment

Release : 16.0
Component: ACF2 for Z/OS

Resolution

There is nothing that can be done in ACF2 to repress these messages since it is a CICS/TS Health Check that is issuing them.

It has been identified by IBM that a CICS XMEOUT exit program must be written for CICS to suppress the DFHHC0801 messages.

Further information from IBM follows.

There are two periods of 30 minutes involved in the health checker messages:

  1. The z/OS health check period, which defaults to 30 minutes for the CICS checks. 
    This means that every 30 minutes, the health checker will check for any messages which have not already been issued and will issue them.

    These will be DFHHxxxx messages which will show up in the S.CK output in TSO. 
    The writing of the DFHHxxxx messages to the S.CK output can have the interval changed by modifying the "interval" specified on the S.CK screen.

    This can be set to ONETIME, which means that the S.CK output will never be updated.
    Then afterwards this change can be made permanent, by modifying the HZSPRMxx member.

  2. The second period of 30 minutes relates to the DFHHCxxxx messages that are issued by CICS to the CICS joblog.

    This interval cannot be changed by customers.
    Using an XMEOUT exit program is the only way to stop the CICS messages from being issued.

Additional Information

Relevant Documentation:

CICS_CAT3_CONFIGURATION

Message domain exit XMEOUT