![[UNIX, Linux, Windows]](ngulw.gif)
Associating a queue manager with an installation
When you create a queue manager, it is automatically associated with the installation that issued the crtmqm command. On UNIX, Linux®, and Windows, you can change the installation associated with a queue manager using the setmqm command.
About this task
The installation that a queue manager is associated with limits that queue manager so that it can
be administered only by commands from that installation. There are three key exceptions:
- setmqm changes the installation associated with the queue manager. This command must be issued from the installation that you want to associate with the queue manager, not the installation that the queue manager is currently associated with. The installation name specified by the setmqm command has to match the installation from which the command is issued.
- strmqm usually has to be issued from the installation that is associated with the queue manager. However, when an IBM® WebSphere® MQ 7.0.1 or earlier queue manager is started on an IBM WebSphere MQ 7.1 or later installation for the first time, strmqm can be used. In this case, strmqm starts the queue manager and associates it with the installation from which the command is issued.
- dspmq displays information about all queue managers on a system, not just
those queue managers associated with the same installation as the dspmq command.
The
dspmq -o installation
command displays information about which queue managers are associated with which installations.
For HA environments, the addmqinf command automatically associates the queue manager with the installation from which the addmqinf command is issued. As long as the strmqm command is then issued from the same installation as the addmqinf command, no further setup is required. To start the queue manager using a different installation, you must first change the associated installation using the setmqm command.
When you want to associate a queue manager with an installation, you can use the
setmqm command in the following ways:
- Moving individual queue managers between equivalent versions of IBM MQ. For example, moving a queue manager from a test to a production system.
- Migrating individual queue managers from an older version of IBM MQ to a newer version of IBM MQ. Migrating queue managers between versions has various implications that you must be aware of. For more information about migrating, see Maintaining and migrating.
Procedure
What to do next
If the installation that a queue manager is associated with has been deleted, or if the queue
manager status information is unavailable, the setmqm command fails to associate
the queue manager with another installation. In this situation, take the following actions:
- Use the dspmqinst command to see the other installations on your system.
- Manually modify the
InstallationName
field of theQueueManager
stanza in mqs.ini to specify another installation. - Use the dltmqm command from that installation to delete the queue manager.