Manage primary and secondary characteristics of DR RDQMs

We can change a secondary disaster recovery replicated data queue manager (DR RDQM) into a primary DR RDQM. We can also change a primary instance into a secondary instance.

You use the rdqmdr command to change a secondary instance of an RDQM into the primary instance. We might need to complete this action if you lose your primary instance for some reason. We can then start the queue manager and carry on running it on the recovery node.

You also use the rdqmdr command to change a primary instance of an RDQM into the secondary instance. We might need to complete this action, for example, if you were reconfiguring the system.

We can also use the rdqmdr on a primary queue manager to retrieve the exact command that we need to create a secondary instance of that queue manager on your recovery node.

We can use the rdqmdr command as a user in the mqm group if the user can use sudo. Otherwise we must be logged in as root.

Procedure

To change a secondary instance of a DR RDQM into a primary instance, enter the following command:
```
rdqmdr -m QMname -p
```
This command fails if the primary instance of the queue manager is still running and the DR replication link is still functioning.
To change a primary instance of the queue manager into a secondary instance, enter the following command:
```
rdqmdr -m QMname -s
```
To display the crtmqm command required to configure the secondary instance of a queue manager, enter the following command on your primary node:
```
rdqmdr -d -m QMname
```
We can enter the returned crtmqm command on your secondary node to create the secondary instance of the RD RDQM.

Parent topic: RDQM disaster recovery