Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

CLUSTER-NODE - define a node application of a UTM cluster application (Unix, Linux and Window systems)

You use the CLUSTER-NODE statement to configure a node application of a UTM cluster application.

You can start up to 32 node applications simultaneously.

You are allowed to specify the CLUSTER-NODE statement up to 32 times for each UTM cluster application.

You must specify at least two CLUSTER-NODE statements if you want to generate a UTM cluster application. A CLUSTER statement must also be generated if you have specified a CLUSTER-NODE statement.

If you change specifications in the CLUSTER statement or the CLUSTER-NODE statements with a new generation, you must create a new cluster configuration file (OPTION GEN=CLUSTER) and use this file to apply the changes.

CLUSTER-NODE

   FILEBASE = node_filebase 
  ,HOSTNAME = host_name
[ ,NODE-NAME = node_name]
[ ,VIRTUAL-HOST = virtual_host_name]

FILEBASE =

node_filebase

Base name of the KDCFILE, the user log file and the system log file SYSLOG for this node application. When a node application is started, the UTM system files are expected under the name specified here. The KDCFILE must be accessible from all node applications.

This operand replaces the FILEBASE start parameter in a standalone UTM application.

The base names of the CLUSTER-NODE statements must differ from each other. The same restrictions apply as for MAX KDCFILE=filebase.

Mandatory operand.

node_filebase identifies the directory containing the KDCFILE and all the files of the application when a node application of a UTM cluster application is started. The name specified here must identify the same directory from the perspective of all the computers of the cluster. The name can be up to 27 characters in length.

HOSTNAME= 

host_name

Host name of this node. Specify the primary name of this host.

The name can be up to 64 characters in length.

The host names of the CLUSTER-NODE statements must differ from each other. Host names that only differ in terms of case are regarded as identical.

In the case of Unix and Linux systems, you must specify the name of the computer that is output by the command uname -n.

On Windows systems, you must specify the name of the computer that is entered in the Control Panel.

No distinction is made between uppercase and lowercase notation; KDCDEF always converts the host names into uppercase.

Mandatory operand.

NODE-NAME=

node_name

Defines a reference name for the node application. This name can be used when configuring LU6.1 sessions as well as for node recoveries:

  • Configuring LU6.1 sessions:
    The reference name defined here can be specified in the NODE-NAME parameter of an LSES statement in order to assign the LU6.1 session unambiguously to a node application. This enables openUTM to select the "right" session when establishing a session with a partner application.

  • Node recovery:
    If a node recovery is to be performed for the node application generated here then the reference name defined here must be specified in the NODE-TO-RECOVER start parameter. For more details, consult "node recovery" in the openUTM manual “Using UTM Applications”.

Default value: NODEnn
nn = 01..32, where nn is determined by the sequence of CLUSTER-NODE statements during generation.

VIRTUAL-HOST=

virtual_host_name

Has the same function as the MAX HOSTNAME parameter with UTM cluster applications. You are not allowed to specify the MAX HOSTNAME parameter in UTM cluster applications.

VIRTUAL-HOST allows the sender address for network connections established from this node application to be specified.

The name can be up to 64characters in length.

Default: blanks. This means that the default sender address of the transport system is used when connections are established.

This function is required in a cluster if the relocatable IP address is to be used as the sender address instead of the static IP address when establishing a connection.

No distinction is made between uppercase and lowercase notation; KDCDEF always converts the virtual host names into uppercase.