IBM Support

PM84671: CPU CONSUMPTION IS HIGHER FOR AN APPLICATION WHEN QM IS RUNNING,ALTHOUGH THE APPLICATION IS NOT BEING MONITORED BY QM.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CPU consumption is higher for an application when QM is running,
    although the application is not being monitored by QM.
    NOTE: The DB2 Query Monitor Collector started task shares code
    with the DB2 Audit Management Expert Collector and the
    InfoSphere Guardium S-TAP Collector started tasks. Customers
    running the Collectors for these products may experience this
    problem in Query Monitor.
    
    Also resolves ABEND0C4 at ADHTCPWZ+A026 or ADHTCPWZ+A15E.
    

Local fix

  • Add an entry in the monitoring profile to capture an exception
    for the workload (ensure that INCLUDE/EXCLUDE is set to a value
    of "I").
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of STAP for DB2 (ADH) V8.1 and     *
    *                 V9.0.                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: CPU consumption is higher for an        *
    *                      application when QM is running,         *
    *                      although the application is not being   *
    *                      monitored by QM.                        *
    *                      NOTE: The DB2 Query Monitor Collector   *
    *                      started task shares code with the DB2   *
    *                      Audit Management Expert Collector and   *
    *                      the InfoSphere Guardium S-TAP Collector *
    *                      started tasks. Customers running the    *
    *                      Collectors for these products may       *
    *                      experience this problem in Query        *
    *                      Monitor.                                *
    *                                                              *
    *                      Also resolves ABEND0C4 at ADHTCPWZ+A026 *
    *                      or ADHTCPWZ+A15E.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Apply the provided ptf.
    

Problem conclusion

  • This apar resolves the reported issue.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM84671

  • Reported component name

    IS GUARD S-TAP

  • Reported component ID

    5655STP00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-12

  • Closed date

    2013-05-01

  • Last modified date

    2013-06-04

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

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

    UK93985 UK93986

Modules/Macros

  • ADH#PLPM ADH#RESM ADH#REST ADH#SSMZ ADHMSACZ
    ADHMSAPZ ADHMSARZ ADHMSASZ ADHMSBCZ ADHMSBPZ ADHMSBRZ ADHMSBSZ
    ADHMSSQZ ADHMS8CZ ADHMS8PZ ADHMS8RZ ADHMS8SZ ADHMS9CZ ADHMS9PZ
    ADHMS9RZ ADHMS9SZ
    

Fix information

  • Fixed component name

    IS GUARD S-TAP

  • Fixed component ID

    5655STP00

Applicable component levels

  • R810 PSY UK93985

       UP13/05/21 P F305

  • R900 PSY UK93986

       UP13/05/21 P F305

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":"SSCA4SV","label":"IBM Security Guardium S-TAP for Db2 on z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1.0","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
04 June 2013