Home

 

Returning a queue manager from MSCS storage

 

This procedure configures the queue manager to be back on its computer's local drive, that is, it becomes a normal WebSphere MQ queue manager. To achieve this, you move the log files and data files from the shared disks. For example, the existing queue manager might have paths such as E:\WebSphere MQ\log\<QMname> and E:\WebSphere MQ\qmgrs\<QMname>. Do not try to move the files by hand; use the hamvmqm utility program supplied as part of WebSphere MQ MSCS Support as described below:

  1. Shut down the queue manager, and check that there are no errors.

  2. Make a full media backup of the queue files and log files and store the backup in a safe place (see Queue manager log files for why this is important).

  3. Decide which local drive to use and ensure that it has sufficient capacity to store the queue manager log files and data (queue) files.

  4. Make sure that the shared disk on which the files currently reside is online on the cluster node to which to move the queue manager log and data files.

  5. Run the utility program to move the queue manager as follows: 
    hamvmqm /m qmname /dd "c:\WebSphere MQ" /ld "c:\WebSphere MQ\log"
    substituting your queue manager name for qmname, your local disk drive letter for c, and your chosen directory for WebSphere MQ (the directories are created if they do not already exist).

  6. Test the queue manager to ensure that it works (as described in Moving a queue manager to MSCS storage).

 

Parent topic:

Removing a queue manager from MSCS control


fa14270_


 

Home