IBM Support

PI71272: WORKLOAD TUNING AT DATASHARING LEVEL MAY FAIL IF ONE OF THE MEMBERS HAS DDF TURNED OFF. CQMC0106E

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When Query Monitor sends (QM) a workload to Query Workload Tuner
    (QWT) for tuning, QM has to tell QWT what database connection to
    use in order to access the EXPLAIN tables. QM will provide
    connection information for a member that QM selects, regardless
    of whether DDF is enabled for that member. If the member that QM
    selects does not have DDF enabled, then workload tuning will
    fail.
    This APAR will do two things:
    1. Users will be able to select, from a "Monitored Database"
    menu
       in QM, which member of the datasharing group should be used
       for the database connection in QWT when tuning this workload.
    2. If the "Staging Table Connection" the user selects in QM is a
       connection to a member in the datasharing group, then the
    menu
       mentioned will default to the member that is used for the
       staging table connection.
    In addition, this APAR resolves the following 3.3 issues:
    - DSM database connections fail to load in the Tuning dialog
    when
    there is a LUW connection defined to DSM
    - Long list of intervals is grouped incorrectly in Archive
    Connection
    - Use of TopN for Data Sharing groups can lead to Index 0: Size
    0:
    message
    - Name of the exported file is too long because interval
    numbers do
    not have concatenation.
    - Export data from a WIN server uses incorrect localization.
    - Workload tuning does not work for dynamic texts in Archive
    Connections
    - Migration of CAE Server public configurations can fail for USS
    - CQMCMGRT sample migration script points to obsolete CQM
    version
    - DSM Truststore set as defalut instead of DB2 Truststore
    - Buttom "Application Menu" disappeared after updating bookmark
    from
    3.2 to 3.3
    - Collecting Host Variables gets SQL Code -103
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of IBM DB2 Query Monitor z/OS.         *
    ****************************************************************
    * PROBLEM DESCRIPTION: When Query Monitor sends (QM) a         *
    *                      workload to Query Workload Tuner (QWT)  *
    *                      for tuning, QM has to tell QWT what     *
    *                      database connection to use in order to  *
    *                      access the EXPLAIN tables. QM will      *
    *                      provide connection information for a    *
    *                      member that QM selects, regardless      *
    *                      of whether DDF is enabled for that      *
    *                      member. If the member that QM selects   *
    *                      does not have DDF enabled, then         *
    *                      workload tuning will fail.              *
    *                      This APAR will do two things:           *
    *                      1. Users will be able to select, from   *
    *                      a "Monitored Database" menu in QM,      *
    *                       which member of the datasharing group  *
    *                       should be used for the database        *
    *                       connection in QWT when tuning this     *
    *                       workload.                              *
    *                      2. If the "Staging Table Connection"    *
    *                       the user selects in QM is a connection *
    *                       to a member in the datasharing group,  *
    *                       then the menu mentioned will default   *
    *                       to the member that is used for the     *
    *                       staging table connection.              *
    *                      In addition, this APAR resolves the     *
    *                      following 3.3 issues:                   *
    *                      - DSM database connections fail to      *
    *                       load in the Tuning dialog when there   *
    *                       is a LUW connection defined to DSM     *
    *                      - Long list of intervals is grouped     *
    *                       incorrectly in Archive Connection      *
    *                      - Use of TopN for Data Sharing groups   *
    *                       can lead to Index 0: Size 0: message   *
    *                      - Name of the exported file is too      *
    *                       long because interval numbers do not   *
    *                       have concatenation.                    *
    *                      - Export data from a WIN server uses    *
    *                       incorrect localization.                *
    *                      - Workload tuning does not work for     *
    *                       dynamic texts in Archive Connections   *
    *                      - Migration of CAE Server public        *
    *                       configurations can fail for USS        *
    *                      - CQMCMGRT sample migration script      *
    *                       points to obsolete CQM version         *
    *                      - DSM Truststore set as defalut         *
    *                       instead of DB2 Truststore              *
    *                      - Buttom "Application Menu"             *
    *                       disappeared after updating bookmark    *
    *                       from 3.2 to 3.3                        *
    *                      - Collecting Host Variables gets SQL    *
    *                       Code -103                              *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI71272

  • 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

    2016-10-25

  • Closed date

    2016-12-16

  • Last modified date

    2017-12-04

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

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

    UI43421

Modules/Macros

  • CQMBLOB  CQMCAEPT CQMCMGRT CQMCPXPT CQMJAR
    CQMMGRF  CQMMGRT
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R330 PSY UI43421

       UP16/12/21 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.

[{"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","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
05 November 2021