IBM Support

PK17815: HIGH CPU USAGE IN CQMMESQL WHEN CQMPARM OPTKEYS(TEXT) IS **NOT**SPECIFIED.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When CQMPARM OPTKEYS(TEXT) is **NOT** specified, high CPU usage
    in CQMMESQL occurs.
    
    This may appear to be a loop in DB2 during processing but is a
    case where QM is adding entries to a pointer chain. as the chain
    grows, more and more CPU is consumed searching the chain.
    
    Customer reported problem running DSNTIAUL program but the error
    can occur with all SQL regardless of the program executing the
    SQL.
    

Local fix

  • Add OPTKEYS(TEXT) parameter to CQMPARMs for affected
    QM Subsystem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Query Monitor.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: When CQMPARM OPTKEYS(TEXT) is **NOT**   *
    *                      specified, high CPU usage in CQMMESQL   *
    *                      occurs. This may appear to be a loop    *
    *                      in DB2 during processing but is a       *
    *                      case where QM is adding entries to a    *
    *                      pointer chain. as the chain grows,      *
    *                      more and more CPU is consumed           *
    *                      searching the chain. Customer reported  *
    *                      problem running DSNTIAUL program but    *
    *                      the error can occur with all SQL        *
    *                      regardless of the program executing     *
    *                      the SQL.                                *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK17815

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    220

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2006-01-12

  • Closed date

    2006-01-25

  • Last modified date

    2006-03-20

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

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

Modules/Macros

  •    CQMCRUDF
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R220 PSY UK11146

       UP06/02/09 P F602

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":"220"}]

Document Information

Modified date:
17 March 2021