PK27397: IN NEAR TERM HISTORY, A THREAD IDENTIFIED AS A PARENT RETURNS MESSAGE "NO PARALLEL TASKS EXECUTED FOR THIS THREAD"

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• For example, look at the historical VSAM logs for the
  following records:
  ================================================================
  ========
  =======
  > THREAD HISTORY SUMMARY
  HATH
  + Report Interval: 15 mins Start: 03/14 12:45:00.000000
  + Report Filtered: NO End: 03/14 12:59:59.999999
  act
  +
  + Not all detail records for this interval are present on the
  data set
  + Elapsed CPU Term
  + End Time Plan Authid Time Time SQL Commit Abrt Pkg Status
  + ------------ -------- -------- ------- ------ ----- ------
  ---- ---
  ------
  + 12:59:48.755 * DISTSERV 242672 6.12 .597 0 8 0 1
  + 12:59:48.582 * DISTSERV 109709 .14 .033 0 8 0 1
  + 12:59:48.438 P DISTSERV 109709 .28 .006 10 1 0 1
  + 12:59:45.470 * DISTSERV 242672 .81 .037 0 8 0 1
  + 12:59:44.655 P DISTSERV 242672 .13 .010 5 1 0 1
  
  Disregard the first record. The second thread seems to be the
  child of
  the third
  and the fourth thread seems to be the child of the fifth. But
  the parent
  thread
  in both cases mentions "No Parallel Tasks executed for this
  thread".
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM                 *
  *                 users of component:                          *
  *                 -   OMEGAMON Server                          *
  *                 -   Classic Interface                        *
  *                 -   CUA Interface                            *
  ****************************************************************
  * PROBLEM DESCRIPTION: 1. Near Term History not displaying     *
  *                         Parent/Child relationships for CPU   *
  *                         Parallel threads.                    *
  *                      2. NTH collect fails to start if old    *
  *                         files are used with new version of   *
  *                         collector.                           *
  *                      3. Dynamic SQL statements for           *
  *                         distributed threads cannot be        *
  *                         displayed when using DSNZPARM        *
  *                         ACCUMACC > 2.                        *
  ****************************************************************
  * RECOMMENDATION: Apply this PTF                               *
  ****************************************************************
  PROBLEM SUMMARY:
  1. Near Term History not displaying Parent/Child relationships
  for CPU Parallel threads.
  2. NTH collect fails to start if old files are used with new
  version of collector.
  3. Dynamic SQL statements for distributed threads cannot be
  displayed when using DSNZPARM ACCUMACC > 2.
  
  PROBLEM CONCLUSION:
  1. Correct logic to match parent to child threads for CPU
  Parallelism.
  2. If incompatible NTH files are detected at collector start-up,
  clear them and start the collector.
  3. Correct logic to match Dynamic SQL with rolled up records
  from ACCUMACC rollup.
  

Problem conclusion

• 1. Correct logic to match parent to child threads for CPU Parall
  2. If incompatible NTH files are detected at collector start-up,
  them and start the collector.
  3. Correct logic to match Dynamic SQL with rolled up records fro
  ACCUMACC rollup.
  
  KEYWORDS : ACCUMACC CPU PARALLELISM  NEAR TERM HISTORY
  

Temporary fix

Comments

APAR Information

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

  OA16141

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

  UK39817 UK39829

Modules/Macros

• HKDB310J HKDB410J KDB310J  KDB410J  KO2ACAPA
  KO2ACAPS KO2ACAP2 KO2ARSBA KO2ARSBS KO2ARSB2 KO2ASPFB KO2ASUBA
  KO2ASUBS KO2ASUB2 KO2ATRPB KO2ATRTB KO2CDSCB KO2CMVSC KO2CMVSF
  KO2CNADB KO2CNAGB KO2CNAPB KO2CNASB KO2CNSRB KO2CNTPA KO2CNTPS
  KO2CNTP2 KO2DAUDA KO2DAUDS KO2DAUD2 KO2DBCIB KO2DCS2B KO2DDSBA
  KO2DDSBS KO2DDSB2 KO2DMSCA KO2DMSCS KO2DMSC2 KO2DTHDA KO2DTHDS
  KO2DTHD2 KO2DXSTB KO2DXS1A KO2DXS1S KO2DXS12 KO2DXS2A KO2DXS2S
  KO2DXS22 KO2HARCB KO2HDTIB KO2HDTPB KO2HINTB KO2HMSGB KO2HPRCB
  KO2HPR1B KO2HPR2B KO2HRCPB KO2HSQIB KO2HSQPB KO2HVINB KO2HWLMB
  KO2ICOLA KO2ICOLS KO2ICOL2 KO2IINTB KO2LCAPB KO2MI00B KO2MSBDB
  KO2MSB1B KO2MSB2B KO2MSB3B KO2MSB4B KO2MSUMB KO2NDRVB KO2OH2IB
  KO2OINTB KO2OMGCB KO2ONAFB KO2ONAGB KO2ONTAB KO2ORCVB KO2OTCCB
  KO2OTCIA KO2OTCIS KO2OTCI2 KO2OTHAB KO2OTHDB KO2OTHFB KO2OTHLB
  KO2OTH3B KO2OTH8B KO2OZM2B KO2PCTCC KO2PCTCF KO2PRECC KO2PRECF
  KO2RSUBB KO2RVSMB KO2SABP  KO2SABS  KO2SACS  KO2SADD  KO2SADS
  KO2SAGB  KO2SAGS  KO2SAPK  KO2SAPS  KO2SAU1  KO2SAU2  KO2SAU3
  KO2SAU4  KO2SAU6  KO2SAU7  KO2SAU8  KO2SSUB  KO2SSUM  KO2TSB1B
  KO2TSB2B KO2TSB3B KO2TSB4B KO2VDINB KO2VIOSB KO2WGETB KO2WINTB
  

Fix information

• Fixed component name

  OM XE DB2PE/PM

• Fixed component ID

  5655OPE00

Applicable component levels

• R310 PSY UK39817

     UP08/09/26 P F809

• R410 PSY UK39829

     UP08/09/26 P F809

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.