PI38657: DFHPG0002 A SEVERE ERROR (CODE X'0B0C') HAS OCCURRED IN MODULE DFHPGLK . YOU GET THIS FOLLOWING ATTEMPTED PURGES OF TASKS.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When one or several tasks are purged, you get message DFHPG0002
  reporting severe error code 0B0C in DFHPGLK .  The KE=1
  formatter shows the following stack:
  .
  01C4   3ACB1920 0740 Dom ...  003954 *Y* DFHPGLK
                       Int ...  0001B4     COMMON_LINK
                       Int ...  000E28     ACQUIRE_FOR_LINK
                       Int ...  0026AC     RELEASE_PROGRAM_LOCK
  01C4   3ACB2060 1120 Dom ...  00460D     DFHMEME
                       Int ...  000296     SEND
                       Int ...  003B04     CONTINUE_SEND
  01C4   3ACB3180 06F0 Dom ...  001AF6     DFHDUDU
                       Int ...  000212     SYSTEM_DUMP
                       Int ...  001084     TAKE_SYSTEM_DUMP
  .
  The key *exc* trace entries for the task are:
  .
  LM 0047 LMLM *EXC* - TASK-REQUESTING-LOCK-HAS-BEEN-PURGED
  FUNCTION(LOCK) LOCK_TOKEN(38E3D3C0) MODE(EXCLUSIVE)
  .
  PG 0B03 PGLK  *EXC* - Recovery - FUNCTION(LINK)
  PROGRAM_NAME(DFHTFP) SYSTEM_AUTOINSTALL(NO)
   (this trace entry shows DFHTFP is the program.  that is not
  important.  it could be any program.  but what is important is
  that it is a PGLK trace entry.  also, the KERRD traced with
  this trace entry shows abendAPGA .
  .
  PG 0B0C PGLK  *EXC* - Get_pglock_error - FUNCTION(LINK)
  PROGRAM_NAME(DFHTFP) SYSTEM_AUTOINSTALL(NO) FUNCTION(LOCK)
  RESPONSE(PURGED)
  .
  In this dump, the PG=1 summary shows that the abending task is
  the owner of the Program Lock for a program (DFHTFP in this
  case.)
  .
  In the aftermath of this dump, the abending task goes away but
  its old PTA address remains the owner of DFHTFP's program lock.
  That causes any task needing DFHTFP's program lock to hang in a
  PROGRAM DFHTFP wait.
  
  Additional Symptom(s) Search Keyword(s): KIXREVDWZ
  
  If the purges are a result of DB2 abending, then this could
  result in the CICS DB2CONN getting stuck in Disconnecting
  status.  This prevents a reconnect with DB2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS Users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: A severe error code x'0B0C' occurs in   *
  *                      module DFHPGLK.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A severe error occurs in DFHPGLK following a purge of a task.
  The task has issued an internal DFHPGLK LINK request to another
  program, in this case DFHTFP. The LINK has obtained the program
  lock for DFHTFP, and whilst it is holding this lock the task is
  purged because DB2 has abended. The task enters recovery but
  will not return a purged response and does not release the
  program lock. The DFHTFP program lock is never freed and any
  other task attempting to obtain this program lock waits. In the
  reported case this resulted in the CICS region remaining in a
  disconnecting state to DB2.
  
  Keywords: abendAPGA APGA PG0002 msgDFHPG0002
  

Problem conclusion

• DFHPGLK's recovery routine has been changed to ensure that when
  a task is purged this response is returned to the caller and the
  program lock is released if it is still being held.
  

Temporary fix

• *********
              * HIPER *
              *********
  FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

  PI35708

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

  UI27426 UI27427

Modules/Macros

• DFHPGAI  DFHPGAQ  DFHPGDD  DFHPGEX  DFHPGIS  DFHPGLD  DFHPGLE
  DFHPGLK  DFHPGLU  DFHPGPG  DFHPGRP  DFHPGST  DFHPGUE  DFHPGXE
  DFHPGXM
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R800 PSY UI27426

     UP15/05/15 P F505 ½

• R900 PSY UI27427

     UP15/05/15 P F505 ½

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.