PM00099: INVALID DATA DUE TO SPLIT RMF TYPE 70 RECORDS IN TABLE MVSPM_CPU_H

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After changing z/OS implementation to use the hiperdispatch
  option, incorrect data is seen in table  MVSPM_CPU_H columns
  MEASURED_SEC, CPU_BUSY_SEC, CPU_DISPATCH_SEC,
  CPU_BUSY_MIPS, MVS_BUSY_SEC.
  The problem appears to be due to split SMF type70 records
  caused by using hyperdispatch.
  Because a SMF record 70 is limited to 32K the number of
  "PR/SM Logical Processor Data Sections" in one record is limited
  to 318 sections. When there are more than 318 PR?SM logical
  processor data sections, a second SMF record 70 is created and
  this split record is not handled correctly.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Decision Support customers who    *
  *                 have split SMF type 70 records, and use      *
  *                 any of the following components:             *
  *                                                              *
  *                 z/OS System (MVS)                            *
  *                 z/OS Performance Management (MVSPM)          *
  *                 Tivoli Performance Modeler for z/OS          *
  ****************************************************************
  * PROBLEM DESCRIPTION: SMF type 70 records can be split over   *
  *                      multiple SMF records, where too many    *
  *                      partitions and logical processors exist *
  *                      to fit into a single SMF record.        *
  *                                                              *
  *                      These split records are not processed   *
  *                      correctly by TDS, resulting in          *
  *                      incorrect data being collected.         *
  ****************************************************************
  * RECOMMENDATION: APPLY THE PTF FIXING THIS APAR               *
  ****************************************************************
  Split SMF type 70 records are not processed correctly by TDS.
  TDS handles each (split) SMF type 70 record as a complete
  record. This causes the following problems:
  
  1. TDS calculates certain values (for example the total weight
  of shared processors) across all partitions. Where these
  partitions are split over multiple SMF records, TDS calculates
  this incorrectly.
  2. TDS uses the information in the Physical partition for
  calculations for all the other partitions. When the SMF type
  70 record is split over multiple records, the Physical partition
  only exists in the last one. This causes TDS to calculate and
  collect data incorrectly.
  

Problem conclusion

• Record procedure DRL2S070 now reassembles the split SMF type
  70 records first, into one complete record (containing all
  partitions and logical processors), before TDS processes the
  records.
  7A0Y
  70AY
  701Y
  710Y
  8A0Y
  801Y
  DRLPMG01
  DRLTMPAS
  DRLTMVSY
  DRL2S070
  

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:

  UK53425 UK53426 UK53427 UK53428 UK53429 UK53430

Modules/Macros

• DRLPMG01 DRLTMPAS DRLTMVSY DRL2S070
  

Fix information

• Fixed component name

  TDS FOR Z/OS

• Fixed component ID

  569510100

Applicable component levels

• R7A0 PSY UK53428

     UP10/01/09 P F001

• R70A PSY UK53429

     UP10/01/09 P F001

• R701 PSY UK53425

     UP10/01/09 P F001

• R710 PSY UK53426

     UP10/01/09 P F001

• R8A0 PSY UK53430

     UP10/01/09 P F001

• R801 PSY UK53427

     UP10/01/09 P F001

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.