Deleting a multi-instance queue manager

Run the WebSphere MQ dltmqm command to delete a queue manager that has instances defined on other servers, on any server where that queue manager is defined. You do not need to run the WebSphere MQ dltmqm command on the same server that you created it on. Then run the WebSphere MQ rmvmqinf or WebSphere MQ dltmqm command on all the other servers which have a definition of the queue manager.

You can only delete a queue manager when it is stopped. At the time you delete it no instances are running, and the queue manager, strictly speaking, is neither a single or a multi-instance queue manager; it is simply a queue manager that has its queue manager data and logs on a remote share. When you delete a queue manager, its queue manager data and logs are deleted, and the queue manager stanza is removed from the mqs.ini file on the server on which you issued the WebSphere MQ dltmqm command. You need to have access to the network share containing the queue manager data and logs when you delete the queue manager. On Windows there is no mqs.ini file; instead, the queue manager stanza is removed from the registry.

On other UNIX platform servers where you have previously created instances of the queue manager there are also entries in the mqs.ini files on those servers. You need to visit each server in turn, and remove the queue manager stanza by running the WebSphere MQ command rmvmqinf Queue manager stanza name. On Windows, run the same command, and the queue manager stanza is removed from the registry.

On UNIX platforms, if you have placed a common mqs.ini file in network storage and referenced it from all the servers by setting the AMQ_MQS_INI_LOCATION environment variable on each server, you need to delete the queue manager from only one of its servers as there is only one mqs.ini file to update.