IBM Support

PM35316: DB2 QUERY MONITOR FOR Z/OS V2R3 FOR DB2 V9 / V10 ISSUES CQM2002EMESSAGE AND WILL NOT COMPLETE STARTUP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 Query Monitor for z/OS V2R3 for DB2 V9 / V10 issues CQM2002E
    message and will not complete startup.  ABEND0C4 may be seen in
    Commit or Rollback.
    A Sample Commit ABEND0C4 seen has a dump title as follows:
    ssid,ABND=0C4-00000011,U=nnnnnnn
    ,M=(N),C=810.SSSC-DSNAPRHX,M=DSNAPRHX,LOC=DSN3AMGP.DSN3SY00+0168
    .
    
    NOTE: The DB2 Query Monitor V2.3 Collector started task shares
    code with the DB2 Audit Management Expert V2.1 Collector and the
    InfoSphere Guardium S-TAP V8.1 Collector started tasks.
    Customers running the Collector with both DB2 Query Monitor and
    DB2 Audit Management Expert or InfoSphere Guardium S-TAP may
    experience this problem.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 Query Monitor.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 Query Monitor for z/OS V2R3 for     *
    *                      DB2 V9 / V10 issues CQM2002E            *
    *                      message and will not complete startup.  *
    *                      ABEND0C4 may be seen in Commit or       *
    *                      Rollback.                               *
    *                      A Sample Commit ABEND0C4 seen has a     *
    *                      dump title as follows:                  *
    *                      ssid,ABND=0C4-00000011,U=nnnnnnn        *
    *                      ,M=(N),C=810.SSSC-DSNAPRHX,M=DSNAPRHX   *
    *                      ,LOC=DSN3AMGP.DSN3SY00+0168             *
    *                      NOTE: The DB2 Query Monitor V2.3        *
    *                      Collector started task shares           *
    *                      code with the DB2 Audit Management      *
    *                      Expert V2.1 Collector and the           *
    *                      InfoSphere Guardium S-TAP V8.1          *
    *                      Collector started tasks. Customers      *
    *                      running the Collector with both DB2     *
    *                      Query Monitor and DB2 Audit Management  *
    *                      Expert or InfoSphere Guardium S-TAP     *
    *                      may experience this problem.            *
    ****************************************************************
    * RECOMMENDATION: APPLY the PTF.                               *
    ****************************************************************
    Code has been changed to correct this condition.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM35316

  • Reported component name

    DB2 QUERY MONIT

  • Reported component ID

    5655E6701

  • Reported release

    230

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2011-03-22

  • Closed date

    2011-04-18

  • Last modified date

    2011-05-02

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

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

    UK66860

Modules/Macros

  •    CQMMAB91 CQMMCM91 CQMMESA1 CQMMES91 CQMMINST
    CQMMPRA1 CQMMPR91
    

Fix information

  • Fixed component name

    DB2 QUERY MONIT

  • Fixed component ID

    5655E6701

Applicable component levels

  • R230 PSY UK66860

       UP11/04/29 P F104

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

Document Information

Modified date:
08 August 2024