Special generation statements are required for generating a UTM cluster application:
You define global properties of a UTM cluster application using the CLUSTER statement. See "CLUSTER - Define global properties of a UTM cluster application". These include, for instance
the cluster filebase
the BCAMAPPL name for cluster-internal communication
timers for monitoring
a failure command and an emergency command to be called if a node fails
specifications on the cluster page pool files (number, warning level, size)
specifications concerning behavior on user sign-on as well as on deadlock handling.
You specify node-specific properties for each node application with the CLUSTER-NODE statement. See "CLUSTER-NODE - Define a node application of a UTM cluster application". These include, for instance
the base name of the KDCFILE, the user log file and the system log file SYSLOG
the host name of the node
the reference name of the node application
You must issue a separate CLUSTER-NODE statement for each node application.
If specifications in the CLUSTER statement or CLUSTER-NODE statements are modified then it is always necessary to create a complete, new generation. This means that the KDCFILE and the cluster files must be regenerated. The only exception are increases in the size of the values for the cluster page pool. For details, see information on enlarging the cluster page pool in the relevant openUTM manual “Using UTM Applications”.
If the UTM cluster files are to be created on generation, you must specify the GEN=CLUSTER parameter in the OPTION statement (see also "OPTION - manage the KDCDEF run").
You must specify MAX BLKSIZE=4K or 8K during KDCDEF generation for UTM cluster applications. For applications on 32-bit systems, the default value is 4K. On 64-bit systems, the default value is 8K.
It is not possible to generate a UTM cluster application with two copies of the KDCFILE, i.e. the value MAX KDCFILE=(..., SINGLE) must be specified (this is the default value).