IBM Support

PH66644: IMPROVE PROCESSING FOR CLEANING UP ANY MESSAGES THAT ARE AWAITING DEFERRED DELETION WHEN THE QUEUE MANAGER IS REMOVED FROM QSG

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CSQ5PQSG VERIFY QSG is returning these messages:
    
    CSQU568E QMGR number mismatch for QMGR XXXX: DB2 value=-1, XCF
    member value=-1, CSQ_ADMIN connection value=0, SMDS group
    value=1
    CSQU568E QMGR number mismatch for QMGR YYYY: DB2 value=-1, XCF
    member value=-1, CSQ_ADMIN connection value=0, SMDS group
    value=5
    
    CSQ5PQSG FORCE QMGR is returning these messages:
    
    CSQU568E QMGR number mismatch for QMGR XXXX: DB2 value=-1, XCF
    member value=-1, CSQ_ADMIN connection value=0, SMDS group
    value=3
    CSQU568E QMGR number mismatch for QMGR YYYY: DB2 value=-1, XCF
    member value=-1, CSQ_ADMIN connection value=0, SMDS group
    value=4
    
    There are messages on the application structure.
    
    These messages are on a deferred delete queue awaiting cleanup
    by the XXXX and YYYY queue managers. However, the queue managers
    were removed from the QSG before they were able to clean up
    their old messages so we will need to manually remove the
    messages from the structure. This can be done by a CSQUZAP.
    
    However, in the case of this application structure, there are no
    apparent messages from the removed queue managers there (XXXX
    and YYYY) so the FORCE QMGR is unable to assist with removing
    the remaining SMDS state from the QSG. Due to this we will need
    to manually remove the queue managers from the QMGR_LIST in Db2.
    In order to do this, it is necessary to run the a SQL which
    should allow the VERIFY QSG operation to complete afterwards.
    
    This APAR was created to improve processing for cleaning up any
    messages that are awaiting deferred deletion when the queue
    manager is removed from the QSG.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 4 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: CSQ5PQSG FORCE QMGR returns RC=04,      *
    *                      accompanied by CSQU587I messages        *
    *                      indicating that the SMDS for one or     *
    *                      more structures is not empty, when      *
    *                      forcibly removing a queue manager from  *
    *                      a queue sharing group, despite all      *
    *                      messages owned by the queue manager     *
    *                      having been deleted from the            *
    *                      structure(s).                           *
    *                      For queue managers already forcibly     *
    *                      removed from the qsg, CSQ5PQSG VERIFY   *
    *                      QSG indicates a QMGR number mismatch,   *
    *                      where the 'SMDS group value' in         *
    *                      CSQU568E contains a positive integer    *
    *                      and differs from the other values in    *
    *                      the message.                            *
    ****************************************************************
    When CSQ5PQSG FORCE QMGR is used to forcibly remove a queue
    manager from the QSG, it will check if each SMDS for that queue
    manager is empty and issue CSQ587I to report if this is not the
    case. If any non-empty SMDS is found the utility returns RC=04,
    and the forced queue manager's id is not made available for
    reuse by a subseqeuent ADD QMGR. Where a queue manager has
    already been removed from the QSG, but one of more CF structures
    still contains messages owned by that queue manager, VERIFY QSG
    will report this as a QMGR number mismatch using message
    CSQU568E.
    In most cases this behaviour is expected, to prevent the queue
    manager id being reused while structures still contain messages
    associated with the removed queue manager. However when messages
    are deleted by a queue manager other than the owning queue
    manager, the deletion is deferred to the owning queue manager so
    that associated SMDS resources can be freed. If the owning queue
    manager is unable to do this, this leads to the SMDS showing as
    non-empty to CSQ5PQSG, even though it only contains deleted
    messages.
    

Problem conclusion

  • CSQ5PQSG FORCE QMGR processing is enhanced to handle deleted
    messages that had the deletion deferred to the queue manager
    being forced.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH66644

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-05-21

  • Closed date

    2026-03-26

  • Last modified date

    2026-05-02

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

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

    UO07274

Modules/Macros

  • CSQ5PQSG
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R400 PSY UO07274

       UP26/04/14 P F604

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":"BU048","label":"IBM Software"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"400","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
02 May 2026