a) No - a queue manager in standby mode is not "open for business". Applications cannot connect to it. If it did issue the STARTCMD for SERVICE objects, the programs that were started would not be able to connect to the queue manager that had started them.
b) This rather depends on how the queue manager ended. You are really asking, "If a QMGR ends, will it issue STOPCMD?". If the queue manager came down hard, clearly it cannot issue STOPCMD. So the answer is "not always". The STOPCMD is actually more useful for when you issue the STOP SERVICE command. Most applications that are used in a SERVICE object, and connect to the queue manager, will detect that the queue manager is coming down and will hopefully end themselves, so there should be no need to rely on the STOPCMD at queue manager end time. Instead just think of that as the way you might manually stop a SERVICE object. You can experiment with different ways of ending/killing a queue manager to test this out yourself without the need for a multi-instance environment.
When the standby instance of the queue manager becomes the live instance, then it will issue STARTCMD.
Cheers,
Morag
------------------------------
Morag Hughson
MQ Technical Education Specialist
MQGem Software Limited
------------------------------
Original Message:
Sent: Tue July 07, 2020 08:22 AM
From: Matthias Jungbauer
Subject: Does Multi-instance queue manager standby do STARTCMD?
Context: Multi Instance + Define Service
https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.1.0/com.ibm.mq.ref.adm.doc/q085740_.htm
Currently I have no access to a multi-instance dev env.
So I cannot test myself.
I had a few questions
a)
If a QMGR starts in standby mode, does it also trigger STARTCMD?
b)
If a QMGR fails over, will it issue STOPCMD at the active one and another STARTCMD at the standby one?
Thank you
Matthias
------------------------------
Matthias Jungbauer
------------------------------