IBM Support

IC78018: WINDOWS PERFORMANCE COUNTER AND WMQ DISPLAY OF QUEUE DEPTH DO NOT MATCH AFTER BACKOUT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After backing out WebSphere MQ messages on a queue, when
    viewing QUEUE DEPTH in Microsoft Windows Performance Counters,
    the value does not match the value of Current Queue Depth as
    displayed in WMQ Explorer or the value for CURDEPTH as displayed
    in runmqsc display queue or display qstatus.
    
    Example One:
    A WMQ queue has one message on the queue.
    - WMQ Explorer Current Queue Depth = 1
    - WMQ runmqsc dis q or dis qs Curdepth = 1
    - Windows Performance Counter Queue Depth = 1
    A MQGET with MQGMO_SYNCPOINT is issued, followed by a backout
    of the MQGET.
    - WMQ Explorer Current Queue Depth = 1
    - WMQ runmqsc dis q or dis qs Curdepth = 1
    - Windows Performance Counter Queue Depth = 0  <<<<----
    .
    Example Two:
    A WMQ queue has zero messages on the queue.
    - WMQ Explorer Current Queue Depth = 0
    - WMQ runmqsc dis q or dis qs Curdepth = 0
    - Windows Performance Counter Queue Depth = 0
    A MQPUT with MQPMO_SYNCPOINT is issued, followed by a backout
    of the MQPUT.
    - WMQ Explorer Current Queue Depth = 0
    - WMQ runmqsc dis q or dis qs Curdepth = 0
    - Windows Performance Counter Queue Depth = 1  <<<<----
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of WebSphere MQ who use Windows Performance monitor to
    monitor performance data of local queues.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    The Windows Performance Monitor interface for WebSphere MQ
    passes incorrect queue statistics, as the queue manager fails to
    update the counter data after MQBACK. Queue manager updates the
    MQ performance monitor counter values only during MQGET, MQPUT
    and CLEAR QL command. Hence after MQBACK performance monitor
    displays incorrect queue statistics.
    

Problem conclusion

  • The WebSphere MQ code has been modified such that the
    performance monitor counter values are updated after MQBACK.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.8
    --------           --------------------
    Windows            U200335
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC78018

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-10

  • Closed date

    2011-11-01

  • Last modified date

    2011-11-01

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

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

Fix information

  • Fixed component name

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023