IBM Support

PI66238: MQ V8 - AFTER A CLEAR QLOCAL COMMAND FOR A SHARED QUEUE, THE SUBSEQUENT MQPUT DOES NOT TRIGGER A NEW MESSAGE FOR THIS QMGR.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A CLEAR QLOCAL command is issued for a shared application queue.
    The queue is defined with trigger type FIRST. The subsequent put
    of a message to this shared queue does not generate a trigger
    message on the queue-manager on which the CLEAR QLOCAL was
    issued.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 8 *
    *                 Release 0 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: After a CLEAR QLOCAL command for a      *
    *                      shared queue, the subsequent MQPUT does *
    *                      not generate a trigger message for this *
    *                      QMGR.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A CLEAR QLOCAL command is issued for a shared queue defined with
    trigger type FIRST. At the end of CLEAR QLOCAL processing the
    queue is closed, and if there are no more applications with the
    queue open, a 'last-closer' broadcast is sent to all
    queue-managers in the group to indicate that the queue is no
    longer open.
    When the 'last-closer' broadcast is processed on each
    queue-manager it should cause list-transition monitoring for the
    queue to be started. However, on the queue-manager on which the
    CLEAR QLOCAL processing was taking place, the 'last-closer'
    broadcast is not processed as the CLEAR QLOCAL thread still has
    a lock on the shared queue. Consequently when a message is later
    PUT to the shared queue, a trigger message is not generated on
    the queue-manager on which the CLEAR QLOCAL was issued.
    

Problem conclusion

  • Module CSQMTAPB has been updated for the reported problem to
    delay processing of the 'last-closer' broadcast if there is a
    lock on the shared queue. Five attempts will be made to obtain
    the lock at quarter second intervals. If the lock is still held
    after this time processing will continue as it did before this
    APAR.
    000Y
    CSQMTAPB
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI66238

  • Reported component name

    WMQ Z/OS 8

  • Reported component ID

    5655W9700

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-21

  • Closed date

    2016-12-20

  • Last modified date

    2017-02-01

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

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

    PI73301 UI43477

Modules/Macros

  • CSQMTAPB
    

Fix information

  • Fixed component name

    WMQ Z/OS 8

  • Fixed component ID

    5655W9700

Applicable component levels

  • R000 PSY UI43477

       UP17/01/27 P F701

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":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 February 2017