PH21051: CICS GROUP ATTACH INSISTS ON RECONNECTING TO DB2 MEMBER THAT WAS QUIESCED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You have 2 DB2 members of a DB2 data sharing group active in
  the same LPAR. A CICS region is connected to one of the
  members. The CICS region's installed DB2CONN includes these attr
  ibutes:
  .
  DB2GROUPID(DB2G)
  STANDBYMODE(RECONNECT)
  RESYNCMEMBER(Y
  ES)
  .
  You shutdown the DB2 member that CICS is connected to by
  doing a STOP DB2 MODE(QUIESCE), or be allowing MODE(QUIESCE) to
  default. The DB2 member shutdown normally.
  .
  Your expectation
  is that CICS will automatically reconnect to the other DB2
  member on the LPAR. But that does not always happen.
  Intermittently, this CICS region insists on reconnecting to the
  just-shutdown member, and so it waits for that member to
  restart.
  .
  Below is an example of the messages when this
  problem happens. (In these examples, the name of the DB2 data
  sharing group is DB2G. The member CICS is connected to (and
  disconnecting from) is DB21. DB22 is the other member of the
  datasharing group on the LPAR.
  ---------------------------------
  ----------------------------------------
  DFHDB2015 12/31/2019
  01:02:03 CICSPRD1 The CICS-DB2 attachment facility is in
  standby for DB2 subsystem DB21
  .
  DFHDB2037 12/31/2019 01:02:03
  CICSPRD1 DB2 subsystem DB21 is not active. The attachment
  facility is waiting.
  -------------------------------------------
  ---------------------------
  .
  When it works as expected the
  messages look like below:
  --------------------------------------
  -----------------------
  DFHDB2015 12/30/2019 01:02:03 CICSPRD1
  The CICS-DB2 attachment facility is in standby for DB2
  subsystem DB2G
  .
  DFHDB2023I 12/30/2019 01:02:03 CICSPRD1 The
  CICS-DB2 attachment has connected to DB2 subsystem DB22 group DB
  2G
  -------------------------------------------------------------
  --
  .
  Additional Symptoms: DFHDB2023
  .
  KIXREVDWZ
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: CICS sometimes insists on reconnecting  *
  *                      to the DB2 Group member that it was     *
  *                      previously connected to.                *
  ****************************************************************
  CICS sometimes insists on reconnecting to the DB2 Group member
  that it was previously connected to. This is because the DB2
  group member was quiesced and the last CICS transaction that
  had used it drove DFHD2STR as part of its commit processing.
  DFHD2STR looked at the UOWs to determine which DB2 group member
  may have to be selected to be connected to. It found this
  transaction and mistakenly believed it had to reconnect to that
  DB2 group member.
  
  Additional Keywords: DFHDB2015 DFHDB2037 msgDFHDB2015
  msgDFHDB2037
  

Problem conclusion

• DFHD2STR has been changed to identify that it is the last task
  in the region that accessed DB2 prior to the group member being
  quiesced. Since its UOW is locally committed this does not
  require CICS to reconnect to the previous DB2 group member that
  was used.
  

Temporary fix

Comments

APAR Information

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

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

  UI67526 UI67527 UI67528 UI67529

Modules/Macros

• DFHD2STR
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R000 PSY UI67526

     UP20/01/25 P F001

• R100 PSY UI67528

     UP20/01/30 P F001

• R200 PSY UI67529

     UP20/01/25 P F001

• R900 PSY UI67527

     UP20/01/28 P F001

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.