Forcing unwanted queue managers to leave a cluster

Force an unwanted queue manager to leave a cluster by issuing the RESET CLUSTER command at a full repository queue manager.

About this task

You can force an unwanted queue manager to leave a cluster. If for example, a queue manager is deleted but its cluster-receiver channels are still defined to the cluster. You might want to tidy up.

Only full repository queue managers are authorized to eject a queue manager from a cluster.

Note: Although using the RESET CLUSTER command forcibly removes a queue manager from a cluster, the use of RESET CLUSTER by itself does not prevent the queue manager rejoining the cluster later. To ensure that the queue manager does not rejoin the cluster, follow the steps detailed in Preventing queue managers joining a cluster.

Follow this procedure to eject the queue manager OSLO from the cluster NORWAY:

Procedure

On a full repository queue manager, issue the command:


RESET CLUSTER(NORWAY) QMNAME(OSLO) ACTION(FORCEREMOVE)

Alternative use the QMID instead of QMNAME in the command:
```
RESET CLUSTER(NORWAY) QMID(qmid) ACTION(FORCEREMOVE)
```
Note: QMID is a string, so the value of qmid should be surrounded by single quotation marks, for example, QMID('FR01_2019-07-15_14.42.42').

Results

The queue manager that is force removed does not change; its local cluster definitions show it to be in the cluster. The definitions at all other queue managers do not show it in the cluster.