RESET CLUSTER

• ¹ Valid only on z/OS when the queue manager is a member of a queue-sharing group.
• ² Valid only on z/OS.

Usage notes for RESET CLUSTER

• On z/OS, the command fails if the channel initiator has not been started.
• On z/OS, any errors are reported to the console on the system where the channel initiator is running; they are not reported to the system that issued the command.
• To avoid any ambiguity, it is preferable to use QMID rather than QMNAME. The queue manager identifier can be found by commands such as DISPLAY QMGR and DISPLAY CLUSQMGR.

  If QMNAME is used, and there is more than one queue manager in the cluster with that name, the command is not actioned.

• If we use characters other than those listed in Rules for naming IBM MQ objects in your object or variable names, for example in QMID, you must enclose the name in quotation marks.
• If you remove a queue manager from a cluster using this command, we can rejoin it to the cluster by issuing a REFRESH CLUSTER command. Wait at least 10 seconds before issuing a REFRESH CLUSTER command, because the repository ignores any attempt to rejoin the cluster within 10 seconds of a RESET CLUSTER command. If the queue manager is in a publish/subscribe cluster, you then need to reinstate any required proxy subscriptions. See REFRESH CLUSTER considerations for publish/subscribe clusters. Note: For large clusters, use of the REFRESH CLUSTER command can be disruptive to the cluster while it is in progress, and again at 27 day intervals thereafter when the cluster objects automatically send status updates to all interested queue managers. See Refreshing in a large cluster can affect performance and availability of the cluster.
• Successful completion of the command does not mean that the action completed. To check for true completion, see the RESET CLUSTER step in Checking that async commands for distributed networks have finished.

Parameter descriptions for RESET CLUSTER

(clustername)

The name of the cluster to be reset. This is required.

ACTION(FORCEREMOVE)

Requests that the queue manager is forcibly removed from the cluster. This might be needed to ensure correct cleanup after a queue manager has been deleted.

This action can be requested only by a full repository queue manager.

CMDSCOPE

This parameter applies to z/OS only and specifies how the command runs when the queue manager is a member of a queue sharing group.

' '

The command runs on the queue manager on which it was entered. This is the default value.

qmgr-name

The command runs on the queue manager you specify, providing the queue manager is active within the queue sharing group.

We can specify a queue manager name, other than the queue manager on which the command was entered, only if you are using a queue sharing group environment and if the command server is enabled.

QMID( qmid )

The identifier of the queue manager to be forcibly removed.

QMNAME( qmname )

The name of the queue manager to be forcibly removed.

QUEUES

Specifies whether cluster queues owned by the queue manager being force removed are removed from the cluster.

NO

Cluster queues owned by the queue manager being force removed are not removed from the cluster. This is the default.

YES

Cluster queues owned by the queue manager being force removed are removed from the cluster in addition to the cluster queue manager itself. The cluster queues are removed even if the cluster queue manager is not visible in the cluster, perhaps because it was previously force removed without the QUEUES option.

On z/OS, N and Y are accepted synonyms of NO and YES.