MQ

Hello MQ group users,

Any advise on the following will be much appreciated.

We have an existing MSCS MQ cluster (2 node setup Active / Passive: w000011880-w000012880)  where two existing QMGRs  (one active running, one test ended)  are already deployed on MQ cluster instance named "A000011880 - IBM MQ"  utilizing a common shared drive ("D: Disk_D") with low space usage.

A new QMGR has been lately (a few days ago) has been created for use with MSCS and added to the above MQ Cluster instance / moving its data & logs to the MSCS shared drive ("D") via hamvmqm command. The new QMGR (NBGCYT24PRD) has been started correctly and listed in the DSPMQ output command:

 According to customer, all steps listed at https://www.ibm.com/docs/en/ibm-mq/9.2?topic=configurations-supporting-microsoft-cluster-service-mscs  such as creating a QM for use with MSCS, Moving QM to MSCS storage, etc:

https://www.ibm.com/docs/en/ibm-mq/9.2?topic=mscs-creating-queue-manager-use

https://www.ibm.com/docs/en/ibm-mq/9.2?topic=mscs-moving-queue-manager-storage 

but  after the patching sheduled for the first cluster node (w000011880) during last weekend and the failover performed from the first (active) node: w000011880 to the second (passive) node: W000012880, the new QMGR is not listed in the DSPMQ command output and also cannot be started as it doesn't exist...

FYI, all QMGR configuration still exists on cluster resource - shared drive "D" in the following path: D:\IBM\MQ\data\qmgrs\NBGCYT24PRD

and recovery logs at D:\IBM\MQ\log\NBGCYT24PRD

Could anybody advise what might be missing? Precise steps (if applicable) will be much appreciated.

Thanks in advance,

Cheers, Nick.

Hi Nick,

I haven't done MQ in MSCS for quite a while, but my recollection is that after moving the files to the shared disk, you have to run a command to actually make the queue manager clustered.

Additional to moving the queue manager to cluster storage, and not mentioned in your list of pages is:

https://www.ibm.com/docs/en/ibm-mq/9.2?topic=mscs-putting-queue-manager-under-control

This documents the steps required in MSCS to make the queue manager managed by the cluster.

Although the queue manager was running on the original server, perhaps it was not actually running under MSCS control.

I would check the cluster configuration and make sure that the cluster does know about the queue manager. Follow the instructions in the manual if it is not.

If it is already known to the cluster then it should also be known to the cluster member, so it sounds like something must have gone wrong in that case, which might call for a case to be raised with IBM.

Regards