New queue introduced in Refresh Pack WebSphere MQ 7.0.1 called SYSTEM.CLUSTER.HISTORY.QUEUE

Resolving The Problem

SYSTEM.CLUSTER.HISTORY.QUEUE is used to store the history of cluster state information. This information is written to the queue when REFRESH CLUSTER is issued, just before the refresh command is processed. This collects the state of the repository cache before it is refreshed. The history may give vital information about any cluster related problems, before it is lost by issuing REFRESH CLUSTER.

Saving the contents of the cluster repository cache into the SYSTEM.CLUSTER.HISTORY.QUEUE before flushing the information using REFRESH CLUSTER is a serviceability feature introduced through WebSphere MQ 7.0.1.0. This operation is invoked only when REFRESH CLUSTER is issued, and therefore it has no performance overhead on the functioning of the queue managers.

There is no specific action required by the customer. If the queue is left untouched (Note: the queue is PUT enabled by default**), the history information will be collected transparent to the users. From serviceability perspective, we do not expect customers to disable the PUT on the SYSTEM.CLUSTER.HISTORY.QUEUE.

History messages are persistent messages. The messages expire after 90 days. However, they remain for another 60 days after that. The queue should never become full as these messages are written only when the REFRESH CLUSTER command is executed and customers should not issue REFRESH CLUSTER until consulting IBM support.

This feature was introduced to improve serviceability of the product.
The information stored in the history queue is for the consumption of IBM support. The information can not be used to rollback the cluster repository state.