IBM Support

PM79820: MQ QUEUE DEPTH LOW (Q_DEPTH_LOW) EVENT IS NOT GENERATED WHEN ALL OF THE MESSAGES ARE EXPIRED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An MQ queue depth hi event occurs due to message buildup after
    the CICS application is shutdown that consumes messages from the
    queue. The messages that are on the queue are non-persistent
    with expiry times. When the CICS application is restarted, an
    MQGet is issued for the queue and no messages are returned due
    to all of the messages expiring. The MQGet has caused the queue
    depth to now be zero which is below the
    queue depth limit but an Q_Depth_Low event is not generated.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 0 Modification 1 and Release 1       *
    *                 Modification 0.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: Q_DEPTH_LOW event is not generated when *
    *                      the low threshold is reached due to     *
    *                      message expiry. QDPHIEV is not          *
    *                      reenabled, and subsequent Q_DEPTH_HIGH  *
    *                      events are not generated.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After the queue depth high (QDEPTHHI) thereshold is reached and
    a Q_DEPTH_HI event is generated, queue depth high events for the
    queue are disabled and queue depth low events are enabled.
    If the queue depth drops below the queue depth low (QDEPTHLO)
    threshold due to messages expiring, no Q_DEPTH_LO event is
    generated, and queue depth high events remain disabled.
    If the queue depth subsequently reaches the high threshold
    again, no Q_DEPTH_HI event is generated.
    

Problem conclusion

  • CSQMGET is changed to call CSQMIAGM to determine whether to
    generate a queue depth low event, even if the get found no
    suitable message, if messages have expired since the last queue
    depth low event was generated.
    010Y
    100Y
    CSQIMGES
    CSQIMGEW
    CSQIMGEX
    CSQMGET
    CSQMIAGM
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM79820

  • Reported component name

    WMQ Z/OS V7

  • Reported component ID

    5655R3600

  • Reported release

    010

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-12-31

  • Closed date

    2013-04-23

  • Last modified date

    2013-07-03

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

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

    UK93700 UK93701

Modules/Macros

  • CSQIMGES CSQIMGEW CSQIMGEX CSQMGET  CSQMIAGM
    

Fix information

  • Fixed component name

    WMQ Z/OS V7

  • Fixed component ID

    5655R3600

Applicable component levels

  • R010 PSY UK93700

       UP13/06/14 P F306

  • R100 PSY UK93701

       UP13/06/14 P F306

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 July 2013