IBM Support


A fix is available


You can track all active APARs for this component.


APAR status

  • Closed as program error.

Error description

  • The customer is running WMQ V7.1 in a 3-way QSG and one of the
    V7.1 Queue Managers terminated. It appears that they have 2
    queues with the same name defined in our environment. This
    causes the following abend:
    Time of Error Information
    PSW: 077C2000 A86AF5F0   Instruction length: 02
                             Interrupt code: 000D
    Failing instruction text: 5810C014 0A0D58F0 C0405810
    Registers 0-15
    01000000 045C6000 00000004 1D4BECF0
    217FCDE0 00000000 217FCDE0 00758888
    00000000 1CE314E0 217FCD80 1D4BECF0
    286B04A0 46BCD248 A86AEBC2 00E50705
    Home ASID: 0160  Primary ASID: 0160  Secondary ASID: 0160
    The 00E50705 means an agent is in a MUST COMPLETE state or is
    holding a latch. The abend occurs in CSQVEUS3 20111013 at
    offset x'14F0' in CSQVEUS3. This problem is that a latch is
    being held unexpectedly:
      Latch Held Mask 01000000 = (8)DMCITREE
    although EBLWLAT is zeroes at the time of the dump.
    The change team reviewed the dump and found the following:
    The abend occurs when a shared queue and a private queue
    with the same name both exist at qmgr startup, and the private
    queue is subsequently deleted after the shared queue.
    During deletion of the private queue, CSQIDDEL detects that a
    shared queue with the same name existed at startup and calls
    CSQILOC2 to locate this queue - this causes a latch to be
    obtained on the IVSA synonym chain.
    If this locate is unsuccessful (i.e. the shared queue has
    already been deleted), the latch is not released.
    When the delete completes, and control returns up the stack
    the latch is still held. This is detected by CSQVEUS3, leading
    to the abend and queue manager termination.

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of WebSphere MQ for z/OS Version 7 *
    *                 Release 1 Modification 0.                    *
    * PROBLEM DESCRIPTION: Deleting a queue can result with abend  *
    *                      5C6-00E50705 being issued at            *
    *                      LOC=CSQVEU3I.CSQVEUS3 due to a latch    *
    *                      being held if a shared queue of the     *
    *                      same name existed at startup (as        *
    *                      reported by message CSQI063E) and this  *
    *                      shared queue no longer exists. This     *
    *                      abend is followed by the queue manager  *
    *                      abnormally terminating 6C6 with         *
    *                      REASON=00E50705.                        *
    * RECOMMENDATION:                                              *
    CSQIDDEL is called to delete the queue, this detects that
    a shared queue with the same name as the queue being deleted
    existed at startup. When this occurs it attempts to locate the
    shared queue, in this process a latch is obtained. As the shared
    queue no longer exists, the locate fails to locate the object.
    If the locate failed, the obtained latch is never freed. When
    CSQIDDEL completes its processing, the remaining latch is
    detected and the abend 5C6-00E50705 is issued.

Problem conclusion

  • In the event that the shared queue, that existed at startup, no
    longer exists when the local queue is deleted, the locate will
    fail. If the locate of the shared queue fails, the latch that
    is obtained before the locate, is now released. This will avoid
    the abend and the queue manager will not terminate abnormally.

Temporary fix

  • *********
    * HIPER *


APAR Information

  • APAR number


  • Reported component name

    WMQ Z/OS V7

  • Reported component ID


  • Reported release


  • Status


  • PE




  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date


  • Closed date


  • Last modified date


  • 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 Z/OS V7

  • Fixed component ID


Applicable component levels

  • R100 PSY UK83910

       UP13/01/16 P F301 Ž

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.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 February 2013