IBM Support

PH61936: CSQU568E ERROR REPORTED WHEN ADDING A QUEUE MANAGER INTO A QSG WHERE IT IS ALREADY DEFINED 24/09/05 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • CSQU568E QMGR number mismatch -SMDS group value=-1 is reported
    when adding a queue manager into a QSG using CSQ5PQSG ADD QMGR
    where it is already defined while the VERIFY QSG reports no
    discrepancies.
    
    Error Reported:
        CSQU546E  Unable to add QMGR XXXX entry, already exists in
    DB2 table CSQ.ADMIN_B_QMGR
        CSQU568E  QMGR number mismatch for QMGR XXXX: DB2 value=7,
    XCF member value=7, CSQ_ADMIN connection value=0, SMDS group
    value=-1
    
        CSQU567E  QMGR XXXX not added to DB2 table due to a number
    mismatch
        CSQU528I  Disconnected from DB2 XXXX
    
        CSQU147I CSQ5PQSG Utility terminated, return code=8
    
    
    The APAR PH53406 added some additional consistency checking to
    the CSQ5PQSG utility to detect some potentially erroneous
    situations where a queue manager could be re-added back into a
    QSG with a different ID number and cause consistency problems
    with SMDS. The new code did not correctly account for the
    scenario where a queue manager is being added back into a QSG
    just to rebuild the XCF group and the queue manager happens to
    have used multiple SMDS datasets. In this case, the new
    consistency checking code will incorrectly report an SMDS
    mismatch of "-1" and will report a failure. However, the
    rebuild of the XCF Group completes before the SMDS checking
    occurs so although the CSQ5PQSG utility will report an error
    and fail with RC=8, the step of re-adding the queue manager
    into XCF should have already been completed. Therefore, if the
    only reason to re-run CSQ5PQSG is to update the XCF Group, then
    the subsequent error "QMGR number mismatch" can be ignored.
    

Local fix

  • None, the "QMGR number mismatch" can be ignored since the
    rebuild of the XCF Group was already completed
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
    *                 Release 2 Modification 0 and                 *
    *                 Release 3 Modification 0.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: After applying the PTF for APAR PH53406 *
    *                      to V9.2 or V9.3, CSQ5PQSG reports the   *
    *                      following error when attempting the     *
    *                      ADD QMGR function, if the queue manager *
    *                      being (re)added has existing SMDS state *
    *                      information for multiple structures in  *
    *                      the ADMIN_B_STRUCTURE table:            *
    *                      "                                       *
    *                      CSQU568E  QMGR number mismatch for QMGR *
    *                      XXXX: DB2 value=3,XCF member value=3,   *
    *                      CSQ_ADMIN connection value=0,SMDS       *
    *                      groupvalue=-1                           *
    *                      "                                       *
    ****************************************************************
    APAR PH53406 added additional validation to CSQ5PQSG to prevent
    queue manager's being added to the qsg if the DB2 records for
    that QSG already contained information for that queue manager
    that was associated with a different queue manager identifier.
    An error in the new checks caused information associated with
    the correct queue manager identifier to incorrectly fail these
    checks when found for multiple structures.
    
    Note that when the queue manager is already in the QSG, and
    CSQ5PQSG ADD QMGR is being issued to add XCF group information
    for the queue manager (for example, in DR scenarios), although
    the utility fails as described, the XCF group information is
    still correctly added.
    

Problem conclusion

  • The consistency checks have been corrected to account for this
    situation.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH61936

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-06-19

  • Closed date

    2024-09-05

  • Last modified date

    2024-10-03

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

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

    PH62907 UI98286 UI98287

Modules/Macros

  • CSQ5PQSG CSQ5PVER CSQFSTXE
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R200 PSY UI98287

       UP24/09/25 P F409 ­

  • R300 PSY UI98286

       UP24/09/25 P F409 ­

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 October 2024