IBM Support

PH22731: CICS EMERGENCY RESTART ALWAYS TRIES TO RECONNECT TO PREVIOUSLY CONNECTED DB2 FOR Z/OS MEMBER.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When CICS is SHUTDOWN IMMEDIATE, the next CICS restart type is
    EMERGENCY. 
     Then when CICS restart type is EMERGENCY and RESYNCMEMBER(YES)
    is specified, CICS requires to reconnect to the previously
    connected Db2 member. This is because Db2 itself may have
    INDOUBT UOWs it wishes to let CICS know about, during the
    connection and resync.
     The process occurs in this way whether or not there are
    indoubt UOWs.
     If the same DB2 member is not available the resync can not
    take place. 
                                                                   .
    This can cause an issue if restarting CICS on a different LPAR,
    and the original Db2 subsystem is not available to reconnect to.
                                                                   .
    DFHSI8440I CICSxxxx Initiating connection to DB2..
    DFHDB2037  CICSxxxx .. DB2 subsystem DBR1 is not active.  The
                          CICS-DB2 attachment facility is waiting..
    DFHSI8443  CICSxxxx Connection to DB2 not completed. Adapter is
                        awaiting initialization of DB2..
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: An emergency restart of CICS always     *
    *                      attempts to connect to previously       *
    *                      connected Db2 subsystem.                *
    ****************************************************************
    In the customers case a CICS region was cancelled, it was
    connected to Db2 subsystem 'A' using group attach. It did not
    have any shunted UOWs.
    This CICS region was then restarted on a different LPAR
    but still required a connection to Db2 subsystem 'A'.
    
    Keywords:
    msgDFHSI8440I SI8440I msgDFHDB2037 DB2037 msgDFHSI8443 SI8443
    

Problem conclusion

  • The CICS Db2 interface has been changed to catalog the MVS
    system name. On a CICS restart, if it is an emergency then if
    the MVS is not the same as the CICS was previously started on
    there is no need to connect to the same Db2.
    
    After APPLYing the PTF associated with this APAR a COLD or
    INITIAL start will be required to update the global catalog's
    Db2 record.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH22731

  • 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

    2020-02-27

  • Closed date

    2020-08-06

  • Last modified date

    2021-10-01

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

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

    UI70929 UI70930 UI70931

Modules/Macros

  • DFHD2CC  DFHD2CM1 DFHD2CO  DFHD2D2  DFHD2DUF DFHD2EX1 DFHD2EX2
    DFHD2EX3 DFHD2IN1 DFHD2IN2 DFHD2MSB DFHD2RL  DFHD2RP  DFHD2ST
    DFHD2STP DFHD2STR DFHD2TM  DFHD2TRI DFHDSMT  DFHSIB1
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R100 PSY UI70931

       UP20/08/07 P F008

  • R200 PSY UI70930

       UP20/08/07 P F008

  • R300 PSY UI70929

       UP20/08/07 P F008

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.

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4"}]

Document Information

Modified date:
02 October 2021