IBM Support

PK90624: DFHRM0120 RESYNC FAIL AND DFHZC2116 DUMP FOR THE LOCALLY COMMITTED UOWS FOR LU61 TASKS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After SYSTEM reset of zOS or cancel of CICS region which use
    LU61 connection, CICS was started EMERGENCY. On the restart of
    CICS, DFHRM0120 RESYNCHRONIZATION INFORMATION FROM THE REMOTE
    SYSTEM NOT SUFFICIENT TO DETERMINE THE OUTCOME OF THE UNIT OF
    WORK and DFHZC2116E RESYNCHRONIZATION FAILED dump was issued.
    The UOW looks already committed before the system rest ( or
    cancel of CICS). CICS write a Commit log with FORCE(YES) but
    write a LINKDELE log FORCE(NO).
    It looks CICS region was lost the (unforced) forget log records
    if CICS canceled before the records were hardened to DFHLOG.
    The UOW should be forget at next restar of CICS. In stead of it,
    CICS try to recover the UOW and get DFHRM0120 and DFHZC2116.
    

Local fix

  • CICS need to be restart with START=INITIAL to remove the UOW.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: DFHZC2116 issued after a DFHRM0120      *
    *                      following a resync across an LU61       *
    *                      connection.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    CICS was connected to IMS via LU61. A task in CICS had started a
    task in IMS and committed. LU61 required that IMS be the Last
    Agent, so it was told to commit by CICS. It did so, and
    instructed CICS to commit in response. CICS locally committed
    the UOW, then told IMS to forget its own recovery information
    for the distributed unit of work. CICS marked the rmlk for
    deletion, and logged the fact by writing an unforced LINKDELE
    record to the system log. The CICS system then terminated before
    this log record was hardened to the logstream. When CICS was
    emergency restarted, the absence of the LINKDELE record meant
    that the rmlk and its UOW were rebuilt by Recovery Manager. The
    LU61 connection was reestablished, and a resync with IMS took
    place. As part of recovery processing, DFHZNAC issued an
    initiate_recovery call to Recovery Manager. This returned the
    fact that the UOW in question was unknown to IMS. It is correct
    that the UOW was unknown, since CICS had previously told IMS to
    forget about it on the earlier run. CICS issued DFHRM0120 to
    record the fact that the resync was unable to determine the
    outcome of the UOW. It then issued DFHZC2116, which resulted in
    an accompanying system dump. Following this, DFHZNAC issued a
    terminate_recovery call and the UOW and link were removed by
    Recovery Manager.
      The customer felt that this diagnostic information was
    unnecessary in this case, since the resolution of the UOW was
    able to be inferred by CICS.
    Keywords: msgdfhrm0120 msgdfhzc2116 rm0120 zc2116 0120 2116
    

Problem conclusion

  • DFHZNAC has been changed to avoid issuing the DFHZC2116 message
    if the initiate_recovery call returns the fact that the link's
    UOW is locally committed.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK90624

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-06

  • Closed date

    2009-07-30

  • Last modified date

    2009-09-02

  • APAR is sysrouted FROM one or more of the following:

    PK82476

  • APAR is sysrouted TO one or more of the following:

    UK49123

Modules/Macros

  • DFHZNAC  DFHZNCA
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R600 PSY UK49123

       UP09/08/15 P F908

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 September 2009