IBM Support

PH01902: CICS DOES NOT AUTOMATICALLY RECONNECT TO DB2 FOLLOWING A DB2 ABEND AND RESTART 18/09/10 PTF PEREMOVE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CICS remains up while DB2 abends and restarts.  CICS does not
    automatically reconnect to DB2.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users with PI98569 applied.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: A CICS DB2 connection may not           *
    *                      automatically reconnect after DB2       *
    *                      outage.                                 *
    ****************************************************************
    Following a DB2 outage the CICS DB2 connection does not happen
    automatically because part of the process to get the connection
    in the correct state is to clean up any protected threads.
    The reconnect task waits on CEX2TERM to know when this cleanup
    has been completed. However the CEX2 transaction suffered an
    abend 0C4 when doing this cleanup leaving the reconnection task
    waiting for CEX2TERM. The 0C4 is the result of DFHD2D2's
    recovery routine trying to clear the TCADB2TK when not having
    addressability, following a failure to associate a TCB.
    
    Keywords: GLB_SERVICE_TASK_STOP_ECB DFHPG0001 msgDFHPG0001
    PG0001 abendAKEX AKEX
    

Problem conclusion

  • UI57402 UI57403 UI57406 UI57407
    The clearing of the TCADB2TK in DFHD2D2s recovery routine is
    first checked for a valid LOT.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH01902

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-08-20

  • Closed date

    2018-09-11

  • Last modified date

    2018-10-02

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

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

    UI58427 UI58428 UI58429 UI58430

Modules/Macros

  • DFHD2D2
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI58430

       UP18/09/14 P F809

  • R100 PSY UI58427

       UP18/09/13 P F809

  • R800 PSY UI58428

       UP18/09/13 P F809

  • R900 PSY UI58429

       UP18/09/13 P F809

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":"5.4","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":"5.4","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 October 2018