obj_type=KC_CLUSTER_NODE

The modifications relate to a node application in a UTM cluster application (Unix, Linux and Windows systems).

In the identification area, you must specify the internal number in the cluster (index of the entry for this node in KC_GET_OBJECT for the object KC_CLUSTER_NODE) of the node application (field kc_name2 in union kc_id_area). In the data area, you must pass the data structure kc_cluster_node_str with the new property values. You can only modify nodes that are not active.

Enter the following in the data structure kc_cluster_node_str:

Field name	Meaning
hostname_long	hostname_long contains the primary host name of the node on which this node application is running. hostname_long can be up to 64 characters in length.
filebase	Base name of the KDCFILE, the user log file and the system log file SYSLOG for the node application. When the node application is started, the UTM system files are expected under the name specified here. This file structure must be accessible from all node applications. The name is passed in the element filebase of type kc_file_base: struct kc_file_base char length[2]; char fb_name[42];
	fb_name	Base name
	length	Length of the base name
	Please note the following when modifying the base name of a node application: The base names of the individual node applications of a UTM cluster application must differ from each other. Specify the directory which contains the UTM system files for the node applications. The name specified here must identify the same directory for all the nodes. It may be up to 27 characters in length.
virtual_host_long	In UTM cluster applications, this has the same function as the HOSTNAME parameter in the MAX generation statement. You may not specify MAX HOSTNAME in UTM cluster applications.
	Specifying virtual_host_long permits the specification of the sender address for network connections established from this node application.

Period of validity / transaction management: type GID ("KC_MODIFY_OBJECT - Modify object properties and application parameters")

The effect is permanent. The information is stored in the cluster configuration file. The modification takes effect immediately and cannot be undone by rolling back the transaction.