IBM Support

DFHAP0002 0D89 in DFHCRIU and DFHRM0002 0377 in DFHRMLSO then CICS crashes

Question & Answer


Question

Why would CICS come down unexpectedly after message DFHAP0002 with severe error code X'0D89' in DFHCRIU followed by DFHRM0002 with severe error code X'0377' in DFHRMLSO? When running with Fault Analyzer, I also receive message IDI0002I reporting an abend AZT8 at offset X'4D34' in DFHZCXR. I'm running CICS Transaction Sever for z/OS (CICS TS) 5.1 and CA Technologies CA-ACF2.

I see these messages in the log:
IDI0002I Module DFHZCXR, CSECT DFHZTSP, offset X'4D34': CICS abend AZT8
DFHAP0002 A severe error (code X'0D89') has occurred in module DFHCRIU
DFHRM0002 A severe error (code X'0377') has occurred in module DFHRMLSO.

The kernel error table shows several AZTO ABENDs, and an AZT8 ABEND.

Trace entries include the following:
AP 1912 RTSU EXC RECOVERY_ENTERED FREE SURROGATE
AP 1712 TFRF EXC Recovery_entered -AB4,RELEASE_FAC,NO,NORMAL
AP 0D89 CRIU EXC RELEASE FACILITY FAILED RM 0377 RMLSO EXC Bad_response_from_client

Answer

CA Technologies has published PTF RO77330 that will stop the abend AZT8 from occurring so CICS will no longer crash.

An AZTO ABEND indicates that the TCTTE ownership chain is in error. An AZT8 ABEND indicates that a terminal control table (TCT) entry for a remotely owned APPC terminal could not be deleted from the TCT. These ABENDs indicate that there is sufficient trouble with the integrity of data that CICS elects to terminate rather than continue.

The trace entry AP 1912 gives the name of the surrogate with a chaining error.

Examining the ownership chain associated with the task that encountered the error, you will find that the cited surrogate is NOT on the ownership chain, however a terminal on the chain has a relay pointer at offset x'84' showing the address of this surrogate. This indicates that the surrogate is a relay link.

Looking at the Table Manager (TM) Domain, you may find that there are READ LOCK BLOCKs for the surrogate containing a task ID that differs from the owning task.

At some point during processing, CA ACF2 performs a DFHTC LOCATE that inadvertently acquires a READ LOCK on the surrogate. At a later time, possibly task termination, CICS attempts to to free the surrogate, and finds it locked, resulting in the ABEND AZT8.

Contact CA Technology support if you need additional help.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"Recovery","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server

Document Information

Modified date:
29 April 2015

UID

dwa1188569