Resolving an HA queue manager left in an indeterminate state

If a power failure occurs when adding a queue manager to a high availability (HA) group, it can leave the queue manager in an indeterminate state.

HA commands can take some time to run. A power failure, or similar disruption, occurring when you are adding an existing queue manager to an HA group can leave the queue manager in an indeterminate state where it is running on neither appliance in the HA pair.

You can resolve this situation by using one of the following methods (the 'local' appliance is the one where you issued the commands that were interrupted).

First, recover the HA status of the queue manager from both appliances by using the status QMName command.

If the queue manager on the local appliance is in a non-HA state and the remote appliance is in a HA state, then complete the following steps:
1. On the remote appliance, enter the following command:
```
dltmqm QMName 
```
2. On the local appliance, enter the following command:
```
sethagrp -i QMName
```
The queue manager will be added to the HA group and run on the local appliance.
If the queue manager on the local appliance is in an indeterminate HA state and the remote appliance is in an HA state, then complete the following steps:
1. On the remote appliance, enter the following command:
```
dltmqm QMName 
```
  You might need to repeat this command several times.
2. On the local appliance, enter the following command:
```
sethagrp -e QMName
```
The queue manager will run on the local appliance as a stand-alone queue manager.