IBM Support

PH09415: PERFORMANCE ISSUE, QM MONITOR COLLECTING TOO MUCH DATA

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • QM profiles defined may not work as expected which may cause QM
    to collect too much data and experience higher CPU consumption.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IBM Db2 Query Monitor z/OS                   *
    *                 users of component                           *
    *                 - CQM ISPF                                   *
    *                 - Monitoring Profiles                        *
    *                 - Summaries                                  *
    *                 - OFFLOAD                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1. Incorrect processing of filters with *
    *                      more than one asterisk caused increase  *
    *                      of collected data in CQM v3.3 comparing *
    *                      with CQM v3.2.                          *
    *                      2. Increased CPU usage after migrating  *
    *                      to Query Monitor v3.3.0 when running    *
    *                      Db2 Query Monitor data offload job,     *
    *                      CQM@LDB2.                               *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    1. Incorrect change of logic for processing filters with more
    than one asterisk caused skip such filters during data
    processing.
    2. During investigation of the structures of the dataset
    interval and the DB2 tables, we determined that the performance
    of unloading data from the datasets of intervals (VSAM) files,
    for loading into a DB2 utility, due to the fact that CQM V3.3
    has more of fields in the file intervals in the DB2 tables and
    fields have a greater length than CQM V3.2.
    

Problem conclusion

  • 1. The logic was corrected to process such filters in the same
    way as in CQM v3.2.
    2. The algorithm of offload process was corrected.
    
    Search Keywords:
    FILTER ASTERISK OFFLOAD CQM@LDB2
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH09415

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    330

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-03-06

  • Closed date

    2019-07-16

  • Last modified date

    2019-08-01

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

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

    UI64223 010PC2Ÿ 010PC2Ÿ

Modules/Macros

  • CQM#SVPA CQM#SVPX CQM@WDB2
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R330 PSY UI64223

       UP19/07/18 P F907

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.

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3.0"}]

Document Information

Modified date:
17 March 2021