REFRESH CLUSTER
Issue the REFRESH CLUSTER command from
a queue manager to discard all locally held information about a cluster.
You are unlikely to need to use this command, except in exceptional
circumstances.
There are three forms of this command:
REFRESH CLUSTER(clustername) REPOS(NO)- The default. The queue manager retains knowledge of all locally
defined cluster queue manager and cluster queues and all cluster queue
managers that are full repositories. In addition, if the queue manager
is a full repository for the cluster it also retains knowledge of
the other cluster queue managers in the cluster. Everything else is
removed from the local copy of the repository and rebuilt from the
other full repositories in the cluster. Cluster channels are not stopped
if
REPOS(NO)is used. A full repository uses its CLUSSDR channels to inform the rest of the cluster that it has completed its refresh. REFRESH CLUSTER(clustername) REPOS(YES)- In addition to the default behavior, objects representing full
repository cluster queue managers are also refreshed. It is not valid
to use this option if the queue manager is a full repository, if used
the command will fail with an error AMQ9406/CSQX406E logged.
If it is a full repository, you must first alter it so
that it is not a full repository for the cluster in question. The
full repository location is recovered from the manually defined CLUSSDR definitions.
After refreshing with
REPOS(YES)has been issued the queue manager can be altered so that it is once again a full repository, if required. REFRESH CLUSTER(*)- Refreshes the queue manager in all the clusters it is a member
of. If used with
REPOS(YES)REFRESH CLUSTER(*)has the additional effect of forcing the queue manager to restart its search for full repositories from the information in the local CLUSSDR definitions. The search takes place even if the CLUSSDR channel connects the queue manager to several clusters.
Note: Use of the REFRESH CLUSTER command
can be disruptive to the cluster while it is in progress, for example
by creating a sudden increase in work for the full repositories as
they process the repropagation of a queue manager cluster resources.
For such reasons it is best to avoid use of the command in day-to-day
work if possible and use alternative methods to correct specific inconsistencies.