Every node application in a UTM cluster application has its own page pool for data that is local to the node. In addition, there is a common cluster page pool for data that is valid globally throughout the cluster. This results in certain special characteristics compared to standalone applications:
Data that applies locally to the node is stored only in the page pool of the relevant node application. Data that applies locally in the node includes, for example, the TLS areas, message queues as well as buffered dialog or asynchronous jobs to transaction codes of TAC classes which have been interrupted due to TAC class control activities.
Data that applies globally throughout the cluster is stored in the cluster page pool. This type of data includes GSSB, ULS or cluster-wide service data.
Properties of the cluster page pool
The cluster page pool forms part of the UTM cluster files and consists of a management file and one or more files containing the user data. The following are defined during generation with KDCDEF:
The size of the cluster page pool file(s)
The number of cluster page pool files
A warning level for the cluster page pool
The message that the value has risen above or fallen below the warning level is always output by the node application that triggered the change of state.
The administration functions permit the following actions:
You can determine the current occupancy of the cluster page pool and reset the statistical values, e.g. by means of WinAdmin, WebAdmin or the KDCADMI program interface.
KC_GET_OBJECT and KC_MODIFY_OBJECT with
obj_type=KC_CLUSTER_CURR_PARYou can increase the size of the cluster page pool files without terminating the UTM cluster application.
openUTM manual “Using UTM Applications for Unix, Linux and Windows systems”, entry for "Increasing the size of the cluster pagepool" in the section "Update generation in a cluster".