A fix is available
APAR status
Closed as program error.
Error description
If we are doing // query rollup and DDF/RRSAF rollup, only the parent task gets counted for a rollup in the DDF/RRSAF block. So if I have thread #1 and it isn't // the QWACPCNT in the cached block will be 1. If I have thread #2 at it goes 100 way //, the count in the DDF/RRSAF rollup cached record will only be bumped to 2. Thus, if there is //ism + DDF/RRSAF rollup, there won't be a way to tell how many children also rolled data into the block. #DBATS field -> ok to do "+qwacpcnt" instead of "+1" when a DBAT rollup record is encountered. (QWACRINV = 1, 2, 3, and QWHCATYP = 8) #NORMAL TERMINAT -> becomes unusable when rollup is used as it is based on a record being cut, and does not have the granularity of what happened to the individual transactions rolled up into the record #CP/X PARALLEL. -> * is incorrect today as it has a value when just regular rollups (without any parallelism) are done * will not be able to tell you how much parallelism is being used if both rollup and // is used for transactions being rolled up
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: OMEGAMON XE for DB2 PE/DB2PM * * users of component: * * - Batch Reporting * * - Performance Database users * * - Performance Warehouse users * **************************************************************** * PROBLEM DESCRIPTION: THE VALUES OF SEVERAL FIELDS OF THE * * HIGHLIGHTS BLOCK OF BATCH ACCOUNTING * * ARE INVALID IN CASE OF DDF/RRSAF THREAD * * DATA * **************************************************************** * RECOMMENDATION: APPLY THIS PTF * **************************************************************** THE CALCULATION OF FOLLOWING FIELDS WAS FORMERLY ONLY BASED ON COUNTING THE QWAC SECTIONS. NOW, IN CASE OF DDF/RRSAF THREAD DATA SOME FIELDS DEPEND ON QWACPCNT, SOME OTHERS CANNOT BE DETERMINED ANY LONGER, AND ADPARLEV MISLEADINGLY SHOWED CP IN CASE OF DDF/RRSAF. AFFECTED FIELDS: ADNOPACK, ASALLIED, ASALLDST, ASDBATS, ASDBATD, ADPARLEV, AND ASPARCPU. AFFECTED COLUMNS OF THE PERFORMANCE DATABASE TABLES ARE RECORDS_NO_PACK, ALLIED, ALLIED_DISTRIBUTED, DBATS, DBATS_DIST, PAR_TYPE, CP_PARALLELISM, AND NORM_ALL_REASONS.
Problem conclusion
THE CALCULATIONS OF THE FIELDS HAVE BEEN CHANGED. KEYWORDS : ADNOPACK ASALLIED ASALLDST ASDBATS ASDBATD ADPARLEV ASPARCPU ASNORMTM RECORDS_NO_PACK ALLIED ALLIED_DISTRIBUTED DBATS DBATS_DIST PAR_TYPE CP_PARALLELISM NORM_ALL_REASONS PDB PWH DDF RRSAF ACCUMAC
Temporary fix
Comments
APAR Information
APAR number
PK42506
Reported component name
OM XE DB2PE/PM
Reported component ID
5655OPE00
Reported release
410
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-04-03
Closed date
2007-04-30
Last modified date
2007-06-04
APAR is sysrouted FROM one or more of the following:
PK37819
APAR is sysrouted TO one or more of the following:
Modules/Macros
DUMM4KO2
SC18998401 |
Fix information
Fixed component name
OM XE DB2PE/PM
Fixed component ID
5655OPE00
Applicable component levels
R410 PSN UK24581
UP07/05/04 P F705
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.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAV2B","label":"IBM Db2 Buffer Pool Analyzer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCT4H5","label":"IBM Tivoli OMEGAMON XE for Db2 PE \/ PM \/ BPA"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"410","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
04 June 2007