Check for new replies
Thread Rating:
  • 62 Vote(s) - 3.02 Average
  • 1
  • 2
  • 3
  • 4
  • 5
RESET CLUSTER - with scenarios and Demo
RESET CLUSTER command is used to forcibly remove a queue manager from a cluster.

The need to use this command is very rare and not required in general.

Reset cluster command can be run only in repository queue manager. This is obvious because a queue manager from cluster has to be removed from full repository.

Some of the scenarios that might need reset cluster are:

• When a queue manager is deleted and it has not been removed from the cluster before it is deleted, full repository will still think that the queue manger is still part of cluster. But in reality , the queue manager doesn't exist at all. So full repository will keep the information for 90 days before removing the entry for the queue manager completely. To update the repository queue manager manually, reset cluster command has to be run.

• A queue manager might be required to be temporarily removed from the cluster. This could be accomplished by removing the queue manager from cluster by normal process which is by suspending, changing the cluster channel attributes etc which is actually suggested. But reset queue manager can be used too to remove the entry in full repository queue manager.
This method could be used if a queue manager is corrupted and removing it from cluster is not a feasible option till the issue is solved.
A refresh cluster command in the queue manager where it is removed will put it back in the cluster when required.



Either queue manager name or QMID of the queue manager to be removed forcefully from cluster can be given.
QMID attribute can be got from queue manager properties.

Dis qmgr QMID

[Image: FpOYAm9.png]

Specifying QUEUES (NO) on a RESET CLUSTER command is the default.
Specifying QUEUES (YES) removes references to cluster queues owned by the queue manager from the cluster. The references are removed in addition to removing the queue manager from the cluster itself.


A queue manager has been deleted without removing it from cluster. Because of this the full repository still has an entry for the queue manager. This entry will be automatically removed after 90 days. To remove it manually we have to run the Reset cluster command.


Full Repository queue manager: QMA
Partial Repository Queue managers: QMB
Cluster Name: ACLUSTER
Listener port for QMA, QMB managers: 1414, 1415

Step 1: Setup clustering

Commands to create the setup:

In QMA Queue manager:

1. Make the Queue manager as full repository:

Alter qmgr repos(ACLUSTER)

2. Create a cluster receiver channel which is shared in cluster.

Define chl(TO.QMA) chltype(clusrcvr) conname(’localhost(1414)’) cluster(ACLUSTER)

In QMB Queue manager:

1. Create the Cluster Receiver channel which is shared in cluster:

Define chl(TO.QMB) chltype(clusrcvr) conname(’localhost(1415)’) cluster(ACLUSTER)

2. Create the Cluster Sender channel to full repository queue manager QMA which is shared in cluster:

Define chl(TO.QMA) chltype(clussdr) conname(’localhost(1414)’) cluster(ACLUSTER)

Step 2: Stop and Delete the queue manager QMB

Endmqm QMB
Dltmqm QMB

[Image: ut2fqkW.png]

Step 3: Check the Queue managers in Cluster ‘ACLUSTER’ in full repository queue manager QMA.

Dis clusqmgr(*)

[Image: q4onaKh.png]

Observe that the queue manager QMB entry is still there in the repository.

Step 4: Remove the queue manager from cluster by reset cluster command and check the the Queue managers in Cluster ‘ACLUSTER’ in full repository queue manager QMA.

Dis clusqmgr(*)

[Image: 9eI6QJY.png]

The QMB queue manager entry in full repository has been removed successfully.

However, removing a queue manager forcibly when it is still in cluster can be recovered by refresh cluster command. This has been explained in refresh cluster post.


Check for new replies

Forum Jump:

Users browsing this thread: 1 Guest(s)