Starting, stopping, and displaying the state of a DR RDQM

You use variants of standard IBM MQ control commands to start, stop, and view the current state of a disaster recovery replicated data queue manager (DR RDQM).


About this task

We must run the commands that start, stop, and view the current state of a replicated data queue manager (RDQM) as a user that belongs to the mqm group.

We must run the commands to start and stop a queue manager on the primary node for that queue manager (that is, the node on which the queue manager is currently running).


Procedure

  • To start a DR RDQM, enter the following command on the RDQM's primary node: 
    strmqm qmname
    where qmname is the name of the RDQM that we want to start.
  • To stop an RDQM, enter the following command on the RDQM's primary node: 
    endmqm qmname
    where qmname is the name of the RDQM that we want to stop.
  • To view the state of an RDQM, enter the following command: 
    dspmq -m QMname
    The state information that is output depends on whether you run the command on the RDQM's primary or secondary node. If run on the primary node then one of the normal status messages returned by dspmq is displayed. If you run the command on a secondary node then the status Ended immediately is displayed. For example, if dspmq is run on node RDQM7, the following information might be returned:
    QMNAME(DRQM8)                         STATUS(Ended immediately)
QMNAME(DRQM7)                         STATUS(Running)
    You can use arguments with dspmq to establish whether an RDQM is configured for disaster recovery, and whether it is currently the primary or the secondary instance: 
    dspmq -m QMname -o (dr | DR)
    One of the following responses is displayed:

      DRROLE()
      Indicates that the queue manager is not configured for disaster recovery.

      DRROLE(Primary)
      Indicates that the queue manager is configured as the DR primary.

      DRROLE(Secondary)
      Indicates that the queue manager is configured as the DR secondary.

Parent topic: RDQM disaster recovery


Related information