IBM Support

PH53406: ENHANCE CSQ5PQSG'S REMOVAL OF QMGR FROM A QSG TO ENSURE THAT FAILED PERSISTENT CONNECTIONS TO THE CF ARE ALSO CLEANED UP

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A problem occurs when a queue manager with failed connections
    to the CF is removed from the QSG (via FORCE command in
    CSQ5PQSG). This leaves a persistent connection that cannot be
    removed via a SETXCF FORCE CONNECTION command for data
    integrity reasons. Deleting the admin structure will resolve
    this but this is not something that customers would want to do
    in a production environment. Therefore an enhancement to the
    FORCE REMOVE of the queue manager in CSQ5PQSG will be
    implemented, so that any connections at that time are cleaned
    up to avoid this problem.
    additional search keyword CSQU568E
    

Local fix

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 forcing a queue manager out of    *
    *                      a queue sharing group (QSG) using the   *
    *                      FORCE QMGR command to CSQ5PQSG, various *
    *                      problems occur when a differently named *
    *                      queue manager is added to the queue     *
    *                      sharing group.                          *
    *                      Problems can include:                   *
    *                      - Abend 5C6-00C5101A in                 *
    *                      CSQELPLM.CSQEMTKN during initial queue  *
    *                      manager startup of the newly added      *
    *                      queue manager, followed by abnormal     *
    *                      termination.                            *
    *                      - The newly added queue manager uses    *
    *                      SMDS's containing the forced queue      *
    *                      manager name                            *
    *                      - DISPLAY SMDSCONN shows the wrong      *
    *                      queue manager name                      *
    *                      - Unexpected/incorrect SMDS spacemap    *
    *                      state                                   *
    ****************************************************************
    When a failed queue manager is removed from a queue sharing
    group using FORCE QMGR the queue manager's connection to the
    admin structure is left as a failed-persistent connection.
    When a different queue manager reuses the same qmid, the failed
    persistent connection causes a notification to be delivered with
    the wrong queue manager name, leading to the CSQEMTKN abend.
    
    When a queue manager is removed from a queue shared group using
    FORCE QMGR, the SMDS state cannot always be cleared from the
    ADMIN_B__STRUCTURE table, causing CSQU587I to be issued.
    When a different queue manager reuses the same qmid, this SMDS
    state causes the wrong queue manager name to be substituted in
    the SMDS name, and can cause various problems using the
    affected SMDS.
    

Problem conclusion

  • The FORCE QMGR command of CSQ5PQSG is changed to clean up any
    failed-persisent connections to the admin structure from the
    queue manager being forced.
    
    The ADD QMGR command of CSQ5PQSG is changed to check for any
    SMDS state relating to a previously forced different queue
    manager, preventing the qmid being reused.
    
    The VERIFY QMGR command of CSQ5PQSG is changed to report if
    any SMDS state for previously forced queue managers still exists
    in the ADMIN_B_STRUCTURE table.
    
    The following updates are made to the IBM MQ Knowledge Centre:
    
    IBM MQ
     Reference
      IBM MQ for z/OS messages, completion, and reason codes
       Messages for IBM MQ for z/OS
        Utilities messages (CSQU...)
    https://www.ibm.com/docs/en/ibm-mq/9.2?
                                 topic=zos-utilities-messages-csqu
    https://www.ibm.com/docs/en/ibm-mq/9.3?
                                 topic=zos-utilities-messages-csqu
    
    CSQU568E
    The message text is changed from:
    "
    QMGR number mismatch for QMGR qmgr-name in queue sharing group
    qsg-name: Db2 value=nn, XCF member value=nn, CSQ_ADMIN
    connection value=nn
    "
    to
    "
    QMGR number mismatch for QMGR qmgr-name in queue sharing group
    qsg-name: Db2 value=nn, XCF member value=nn, CSQ_ADMIN
    connection value=nn, SMDS group value=nn'
    
    The System programmer response has the following added:
    "
    If the SMDS Group number is -2, SMDS state information exists
    for the QMGR number for a different queue manager. Use the
    CSQ5PQSG utility with "VERIFY QMGR" parameter to identify the
    queue manager associated with the SMDS state, followed by
    "ADD QMGR" to readd the associated QMGR, then retry the original
    "ADD QMGR" command.
    
    If the SMDS Group number is -1, SMDS state information exists
    for a queue manager with multiple qmids.  Collect the items
    listed in the Coupling Facility problem determination guide and
    contact your IBM support center.
    "
    
    
    
    CSQU559I is added:
    "
    CSQU559I
    CSQ_ADMIN connection deleted for QMGR qmgr-name
    
    Explanation
    Informational message indicating that a failed-persistent
    connection to the admin structure was successfully deleted.
    "
    

Temporary fix

Comments

  • ×**** PE24/06/19 FIX IN ERROR. SEE APAR PH61936  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PH53406

  • Reported component name

    IBM MQ Z/OS V9

  • Reported component ID

    5655MQ900

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-03-21

  • Closed date

    2023-11-22

  • Last modified date

    2024-09-05

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

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

    UI94577 UI94578 UI94579 UI94580 UI94581 UI94582 UI94583 UI94584
    UI94585 UI94586

Modules/Macros

  • CSQ5PQSG CSQ5PVER CSQFSTXC CSQFSTXE CSQFSTXF CSQFSTXK CSQFSTXU
    

Fix information

  • Fixed component name

    IBM MQ Z/OS V9

  • Fixed component ID

    5655MQ900

Applicable component levels

  • R200 PSY UI94577

       UP24/01/18 P F401 ¢

  • R202 PSY UI94578

       UP24/01/18 P F401 ¢

  • R203 PSY UI94579

       UP24/01/18 P F401 ¢

  • R204 PSY UI94580

       UP24/01/18 P F401 ¢

  • R205 PSY UI94581

       UP24/01/18 P F401 ¢

  • R300 PSY UI94582

       UP24/01/18 P F401 ¢

  • R302 PSY UI94583

       UP24/01/18 P F401 ¢

  • R303 PSY UI94584

       UP24/01/18 P F401 ¢

  • R304 PSY UI94585

       UP24/01/18 P F401 ¢

  • R305 PSY UI94586

       UP24/01/18 P F401 ¢

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

Document Information

Modified date:
06 September 2024