Adjusting the cluster version of a cluster

The cluster version defines the level at which all the nodes in the cluster are actively communicating with each other.

Cluster versioning is a technique that allows the cluster to contain systems at multiple release levels and fully interoperate by determining the communications protocol level to be used.

To change the cluster version, all nodes in the cluster must be at the same potential version. The cluster version can then be changed to match the potential version. This allows the new function to be used. It cannot be decremented without deleting the cluster and re-creating it at a lower version. The current cluster version is initially set by the first node that is defined in the cluster. Subsequent nodes added to the cluster must be equal to the current cluster version or the next level version; otherwise, they cannot be added to the cluster.

If you are upgrading a node to a new release, you must ensure that the node has the appropriate cluster version. Once the nodes are at a new release and all nodes have a higher potential cluster version than the current cluster version, upon issuing the STRCLUNOD command the version is automatically upgraded. This ensures that all functions associated with the new release are available.