Files

Both files that are global to the cluster and files that are local to the node belong to the runtime environment of the UTM cluster application.

You specify in the storage location of the files during UTM generation using the following KDCDEF statements:

• CLUSTER CLUSTER-FILEBASE = cluster_filebase
  cluster_filebase identifies the storage location of the UTM cluster files.

• CLUSTER-NODE FILEBASE = node_filebase
  node_filebase identifies the storage location of the files local to the node.

You must specify cluster_filebase for the application run when the node applications are started using the start parameter CLUSTER-FILEBASE = cluster_filebase. The same value must be specified for this start parameter for all node applications.

The value that you specified for cluster_filebase during UTM generation does not have to match the value that you specify for cluster_filebase using the start parameter.

It is crucial that the UTM cluster files, such as the cluster configuration file, are available under the base name (cluster_filebase) specified in the start parameters at the time at which the first node application is started.

UTM cluster files

A number of files that can be accessed jointly by all node applications are required in order to run a UTM cluster application. These UTM cluster files are created in a base directory specific to the UTM cluster application (cluster_filebase).

The following list indicates all the UTM cluster files. In this list, the file names are specified without base directory. The complete name in each case is as follows:

cluster_filebase/UTM-C.xxxx on Unix and Linux systems

cluster_filebase\UTM-C.xxxx on Windows systems

xxxx=CFG, USER, ..., LOCK

UTM-C.CFG *)	Cluster configuration file Contains the configuration of the cluster, the current status of all the nodes of the cluster, additional information on all the node applicationsof the UTM cluster application and specifications on data that is global to the cluster.
UTM-.USER *)	Cluster user file Contains user-specific information for managing users in a UTM cluster application. In a UTM cluster application without explicitly generated user IDs, the cluster user file is not needed and is therefore not generated.
UTM-.CP nn *) (nn = 01, ..., 10)	Cluster page pool files, the number of which is defined during UTM generation. Contain user data that is managed globally throughout the cluster in UTM cluster applications (GSSB, ULS and the service data of users).
UTM-C.CPMD *)	Control file for the cluster page pool
UTM-C.GSSB *)	Cluster GSSB file Used for GSSB management in a UTM cluster application
UTM-C.ULS *)	Cluster ULS file Used for ULS management in a UTM cluster application.
UTM-C.JRN1 UTM-C.JRN2	Administration journal which logs global administration actions ("memory" for the administration functions, see section "Administration journal"). openUTM uses these files to ensure that global administrative changes apply globally and consistently across the entire cluster.
UTM-C.JKAA	Journal file containing a copy of the KDCS Application Area (KAA). Administrative changes which are no longer contained in the administration journal (see section "Administration journal") are taken from this file.
UTM-C.LOCK	Cluster lock file Used for the management of queues in a UTM cluster application.
UTM-C.SLCK	Lock file for serialization of the start phase of the node applications.

The UTM cluster files indicated by *) are created by KDCDEF at generation time (see section "UTM generation").

The journal files (.JRN1, .JRN2, .JKAA) and the lock files are set up by openUTM the first time the first node application is started.

CAUTION!

You must not rename any of these files or copy them to a different location. This applies during operation of the UTM cluster application and after the UTM cluster application has been terminated.

Files local to the node

Both files that are global to the cluster and files that are local to the node belong to the runtime environment of the UTM cluster application. A filename prefix that is unique within the cluster (node_filebase) is assigned to each node in the case of files that are local to the node. There are the following files local to the node for each node application:

• the KDCFILE files (including the pagepool and restart areas) in the form of copies of the initial KDCFILE files:

  node_filebase /KDCA

  node_filebase \KDCA

  node_filebase /PxxA
  node_filebase \PxxA

  if required by the UTM generation

  node_filebase /RxxA
  node_filebase \RxxA
  if required by the UTM generation

  The initial KDCFILE files are created using KDCDEF (see section "UTM generation"). You must copy these files for each node application.

  You must organize the KDCFILEs of the node applications in such a way that all KDCFILEs of the node applications can be accessed by all other node applications.

• System log file (SYSLOG file)

  node_filebase /SYSLOG
  node_filebase \SYSLOG

  The system log file SYSLOG can be a single file or a file generation group (FGG).

• User log file

  node_filebase /USLA
  node_filebase \USLA

  The user log file USLOG must be a file generation group (FGG).

• Execution logs

  • Diagnostics files

  • Other application-specific files

You must set up the SYSLOG file and the user log file and other application-specific files for each node application.

You can maintain different versions of the application program on Unix, Linux and Windows systems. The same version of the application program must, however, be loaded on all running node applications with a KDCFILE from the same generation run.