PM01454: CICS REGION DOES NOT RECONNECT TO DB2 AFTER A DB2 CRASH.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CICS did not reconnect to DB2 after DB2 Crash. You see the
  following messages in the CICS log:
  DFHAP0002 A severe error (code X'31B4') has occurred in module
            DFHD2STP
  DFHAP0002 A severe error (code X'31C4') has occurred in module
            DFHD2STR
  DFHAP0002 A severe error (code X'3145') has occurred in module
            DFHD2TM
  In module DFHD2STP when in Stop_DB2_connection the
  glb_in_standby bit is set so we are not driving disable_true,
  but instead we are driving remove_purgeable_from_true, which
  then goes onto do a DISABLE call, which then results in a
  security (CHECK_CICS_COMMAND) call. On the enable we will again
  be issuing the security checking.
   Additional Symptom(s) Search Keyword(s): KIXREVEAA
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All.                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: A severe error (code X'31B4') has       *
  *                      occurred in module DFHD2STP.            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Following a DB2 crash the CICS DB2 attachment was driven to
  put the attachment back into a waiting state for the restart
  of the DB2 subsystem. This requires an EXEC CICS DISABLE call,
  but the call is made under a user transaction that does not
  necessarily have the correct security access to perform the
  DISABLE and the DISABLE receives a NOTAUTH response which
  results in the severe errors in DFHD2STP, DFHD2STR and DFHD2TM.
  These errors are accompanied by msg DFHAP0002.
  
  Additional Keywords: AP0002 0002 31B4 31C4 3145
  TID_D2STP_DISABLE_PROGRAM_FAIL TID_D2STR_ENABLE_PROGRAM_FAIL
  TID_D2TM_START_DB2_FAIL"
  

Problem conclusion

• DFHD2STR and DFHD2STP have been changed to turn CMDSEC and
  RESSEC checking off around the SPI calls.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  PM02808 UK54029

Modules/Macros

•    DESD2STP DESD2STR DFHD2STP DFHD2STR
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R500 PSY UK54029

     UP10/02/04 P F002

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.