MQ

 View Only
Expand all | Collapse all

zOS: Needed Queue Sharing Group recycle after the full Db2 Sharing Group outage?

  • 1.  zOS: Needed Queue Sharing Group recycle after the full Db2 Sharing Group outage?

    Posted Fri November 19, 2021 07:44 AM
    Hello team,

    we have mainframe environment where two MQ subsystems are connected into the Queue Sharing Group (QSG) (with associated Db2 Data Sharing Group (DSG)) and MQ Cluster. When an outage of one Db2 member of DSG happen then associated MQ subsystem waits and after the Db2 member is available again the MQ-Db2 connection is restored and affected MQ subsystem could continue to work without recycle.

    But when the full Db2 DSG become unavailable the MQ connection to Db2 (means QSG <> DSG) is completely lost and any MQ subsystems cannot restore their connections to Db2 DSG members after the Db2 DSG become available again. It is necessary to stop/start (recycle) all MQ subsystems connected to affected QSG to restore their connection to Db2.

    Could you, please, confirm that this mechanism works as designed?
    Is there any way how to prevent the necessity to recycle MQ subsystems after the full Db2 DSG outage?
    If not, is there any MQ message informing us that the full Db2 outage happened and it is necessary to recycle the MQ subsystem?

    Thank you for your statement or help!

    Best regards,

    Radek Vanek
    zSeries DB2 / MQ Specialist



  • 2.  RE: zOS: Needed Queue Sharing Group recycle after the full Db2 Sharing Group outage?

    IBM Champion
    Posted Thu December 02, 2021 02:58 PM
    See Matt Leming's reply here https://listserv.meduniwien.ac.at/cgi-bin/wa?A2=MQSER-L;e5f3cdb6.2112&S=

    ------------------------------
    Francois Brandelik
    ------------------------------

    Original Message