Starting a UTM cluster application

On Unix and Linux systems: Before starting the application, set the environment variable LD_LIBRARY_PATH and, if necessary, LD_LIBRARY_PATH64 to indicate the directories containing the employed shared objects if you have not been able to use uniform installation paths (see also "Installing the UTM runtime components for Unix and Linux systems").

You start a UTM cluster application by starting one or more node applications. You start each node application separately in the same way as a standalone application (see the section "Starting a UTM application on Unix and Linux systems" and the section "Starting a UTM application on Windows systems").

Start parameter file

In contrast to a standalone UTM application, the start parameter file must contain the statement START CLUSTER-FILEBASE=cluster_filebase in place of the statements START FILEBASE=filebase.

The following start parameters apply globally to the cluster:

• TESTMODE

• BTRACE

• OTRACE

• DUMP-MESSAGE

• interval value for SYSPROT

Start parameters which apply globally to all nodes are distributed from the first node application started to nodes which start subsequently via the administration journal. They remain valid – even during or after an update generation – until the UTM cluster application is terminated or until the value is changed using the administration functions.

If the node applications do not require any special start parameters, the start parameter file can be the same for all node applications. The UTM cluster files generated by KDCDEF must be present under the base name which you specified for CLUSTER-FILEBASE. These files must come from the same generation run (see the section "Creating the startparameter file" (Preparation for use)). The files of the KDCFILE must not be older than the UTM cluster files.

When a node application is started, the following cluster-specific start actions are performed:

• A check is performed whether the KDCFILE of the node application is compatible with the cluster configuration file.

• The first time the first node application is started, the administration journal files are initialized and the cluster lock file and the serialization file (UTM-C.SLCK) are set up.

• Cluster monitoring in which the node applications monitor each other is started when a second node application is started.

• Cluster monitoring is automatically extended when a further node application is started.

• The monitoring relationships are determined dynamically (see the section "Application monitoring of the node applications").

SYSLOG file and user log file

You must set up the system log file SYSLOG and the user log file for each node application (see the sections "System log file SYSLOG" and "User log file").

The system log file SYSLOG must either be set up as a single file on all nodes or must be set up as a File Generation Group (FGG) on all nodes (see "System log file SYSLOG").

All running node applications with a KDCFILE from the same UTM generation run must have the same SYSLOG configuration, otherwise startup of a subsequent node is aborted.

Encryption capability

You must ensure that the appropriate openSSL library is provided on all nodes.