IBM Support

PH61721: CSQU568E QMGR NUMBER MISMATCH FOR QMGR XXXX: DB2 VALUE=1, XCF MEMBER VALUE=0, CSQ_ADMIN CONNECTION VALUE=0, SMDS GROUP VALUE=-1

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CSQ5PQSG ADD QMGR results in
    
    CSQU568E  QMGR number mismatch for QMGR XXXX: DB2 value=1, XCF
    member value=0, CSQ_ADMIN connection value=0, SMDS group
    value=-1
    CSQU567E  QMGR XXXX not added to DB2 table due to a number
    mismatch
    
    It is not possible the add the queue manager into QSG.
    
    The specific reason for the CSQU568E message is because there
    are structures that still have references to the old queue
    managers even though they have been deleted from the QSG.
    
    This is because of some of the complexities when attempting to
    remove an SMDS dataset that mean it is now difficult for the
    utility that removes queue managers from the QSG to check and
    verify whether there are still any messages on the structure
    that are offloaded to the SMDS. Because of this the utility is
    currently unable to safely remove SMDS datasets from the QSG
    even when the queue manager itself is forced out. This is
    documented but causes subsequent problems when attempting to
    re-add queue managers back into the QSG.
    
    This APAR was raised to provide a code enhancement to the
    CSQ5PQSG utility that would allow it to do some additional
    checks during queue manager removal to determine whether the
    references to the SMDS dataset can be safely removed. This will
    allow customers to more cleanly remove queue managers from a
    QSG provided they can remove the associated messages first.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 3 Modification 0 and                 *
    *                 Release 4 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: CSQU587E incorrectly reports that the   *
    *                      SMDS associated with an application     *
    *                      structure was not empty when a queue    *
    *                      manager is forcibly removed from a      *
    *                      Queue Sharing Group by the FORCE QMGR   *
    *                      function of CSQ5PQSG, if the forced     *
    *                      queue manager was connected to the      *
    *                      structure when last stopped, and did    *
    *                      not stop cleanly.                       *
    *                                                              *
    *                      Attempts to add another queue manager   *
    *                      to the QSG subsequently fail with       *
    *                      CSQU586E due to the remaining SMDS      *
    *                      state.                                  *
    ****************************************************************
    When CSQ5PQSG FORCE QMGR is used to forcibly remove a queue
    manager for a queue sharing group, a check is made on the SMDS
    spacemap for each application structure.
    If the spacemap indicates that the SMDS for the queue manager is
    not empty, CSQU586E is issued and the SMDS state is not removed,
    preventing the same qmid being reused for a differently named
    queue manager.
    However, when the queue manager was not stopped cleanly (as can
    be expected when using FORCE QMGR) the spacemap for any
    structures that were connected at the time will be left in an
    'active' state, even if no messages were offloaded to the SMDS
    at that time.
    

Problem conclusion

  • The FORCE QMGR function of CSQ5PQSG is changed to scan the
    contents of each application structure with SMDS state to
    determine if it contains any messages offloaded by the queue
    manager being forcibly removed.
    If none are found on either shared queues or internal lists in
    the structure, indicating that the SMDS is empty, the SMDS state
    for the queue manager is removed from the structure table.
    
    CSQ5PQSG FORCE QMGR can now be rerun for a named queue manger to
    remove state that could not removed on the initial execution.
    FORCE QMGR will return 0 if all state that it could detect (DB2,
    XCF, Structure Backups, SMDS) relating to the queue manager has
    been removed, and 4 if some state relating to the queue manager
    remains.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH61721

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-06-06

  • Closed date

    2024-12-12

  • Last modified date

    2025-02-03

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

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

    UI99393 UI99394

Modules/Macros

  • CSQ5AUTL CSQ5B930 CSQ5B940 CSQ5PQSG
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R300 PSY UI99394

       UP25/01/07 P F501

  • R400 PSY UI99393

       UP25/01/07 P F501

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":"300","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
03 February 2025