IBM Support

PI73301: MQ V9 - 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 IBM MQ for z/OS Version 9 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 an
    exclusive lock on the shared queue, processing continues when
    the lock is freed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI73301

  • Reported component name

    MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    000

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-12-06

  • Closed date

    2016-12-20

  • Last modified date

    2017-03-02

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

    PI66238

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

    UI44067

Modules/Macros

  • CSQMTAPB none
    

Fix information

  • Fixed component name

    MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R000 PSY UI44067

       UP17/02/08 P F702

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":"9.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
02 March 2017