PI68131: MONITORING FIELDS KY8DISPT AND QRDISPT CONTAIN INVALID VALUES FOR CICS LIBERTY TASKS 16/11/22 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The CICS monitoring fields KY8DISPT and QRDISPT contain invalid
  values when running CICS Liberty tasks. It appears that there
  are store clock type values.
  
  This is being caused by the Liberty threadpooling changes in
  V5.3. For Liberty, when the task ends, its T8 TCB is now being
  put back into a pool for the Liberty JVM server to reuse.
  Consequently it is now on the T8 when it goes through a 'normal'
  transaction attach and detach.
  
  At the end of a task we are stopping the correct dispatch time
  clock (either QR or T8). We're not doing that during the
  transaction build though, so the QR dispatch is always being
  started.
  

Local fix

• not available
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All CICS users with UI37614 applied.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * CICS performance monitoring data clock fields show incorrect *
  * values for CICS Liberty transactions.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * .                                                            *
  ****************************************************************
  The CICS performance monitoring data records for transactions
  which ran in a Liberty JVM server inside CICS can be incorrect.
  For example the KY8DISPT may contain a stored clock value. The
  problem occurs because the QR dispatch clock is always the one
  started in BUILD_TRANSACTION, but a Liberty threadpool task may
  be running on a T8 TCB at this time.
  A further problem exists which causes too much CPU time to be
  attibuted to the user transaction in the KY8CPUT field. This is
  because the transaction could record some time used by the TCB
  while that TCB was in the Liberty threadpool.
  Additonal Keywords: KY8CPUT QRDISPT
  

Problem conclusion

• UI37614 UI39577
  DFHMNXM has been updated to ensure that transactions which begin
  on a T8 TCB will initially start the T8 dispatch and CPU clocks.
  Furthermore, DFHKETA has been updated to ensure that a user
  transaction does not record time spent on that TCB before this
  transaction was started.
  

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:

  UI43335

Modules/Macros

• DFHAPDUF DFHAPSDF DFHAPSI  DFHAPXM  DFHBRDUF DFHCQSY  DFHDBDUF
  DFHDPDUF DFHEJDUF DFHERM   DFHKETA  DFHMNDUF DFHMNXM  DFHMPDUF
  DFHPGDUF DFHREST  DFHSODUF DFHTKDUF DFHTMDUF DFHUEDUF DFHUSDUF
  DFHW2DUF DFHWBDUF DFHXMAB  DFHXMAT  DFHXMBD  DFHXMCL  DFHXMDD
  DFHXMDM  DFHXMDU2 DFHXMDUF DFHXMER  DFHXMFD  DFHXMIQ  DFHXMLD
  DFHXMQC  DFHXMQD  DFHXMRL  DFHXMRM  DFHXMRM1 DFHXMRP  DFHXMRSD
  DFHXMRU  DFHXMSR  DFHXMST  DFHXMTA  DFHXMXD  DFHXMXE  DFHXMXM
  

Fix information

• Fixed component name

  CICS TS Z/OS V5

• Fixed component ID

  5655Y0400

Applicable component levels

• R000 PSY UI43335

     UP16/12/29 P F612 {

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.