PI93686: DB2 RUNSTATS HANG AFTER HAVING THE UI44914 APPLIED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A RUNSTATS job running with a zIIP configuration hung when the
  Db2 regions were executing with UI44914 active but the batch job
  did not have the ptf in its step libraries.  The thread that
  does a put to a pipe was suspended at DSNUSTBL UI49484+7881,
  while the thread that does the get from a pipe was suspended at
  DSNUGLSR UI43340+2F71. The put thread was not resumed after
  data was retrieved from the pipe.
  
  This condition will only occur when UI44914 is active for the
  started tasks but the batch job is running at a lower
  maintenance level that does not have UI44914 in a ziip
  configured environment.
  
  This could also happen for other utilities that have inline
  stats specified.
  

Local fix

• Use the same SDSNLOAD file for the batch utility job that the
  started tasks are using. In a mixed level data sharing
  environment, use the highest level of SDSNLOAD for the batch
  job.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Db2 11 for z/OS utility users with zIIPs *
  *                 using RUNSTATS or inline statistics with     *
  *                 PTF UI44914 installed in DBM1 but not in     *
  *                 batch.                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION: RUNSTATS hang when running on a zIIP    *
  *                      enabled system when PTF UI44914 for     *
  *                      APAR PI73882 has been installed and     *
  *                      activated for the DBM1 address space    *
  *                      but not for the batch address space.    *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available          *
  ****************************************************************
  Communication between batch and DBM1 address spaces for RUNSTATS
  or inline statistics was waiting for a flag to get set by batch
  when running in zIIP enabled mode. Due to missing maintenance in
  batch this flag was never set and caused a hang.
  

Problem conclusion

• Code has been changed to correctly handle missing maintenance
  in the batch address space.
  

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:

  UI54653

Modules/Macros

•    DSNURBXA DSNURBXC DSNURULN DSNURWBF DSNURWBR
  DSNUSTBL
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI54653

     UP18/04/06 P F804 Ø

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.