Converting a UTM cluster application to a standalone UTM application

If you want to convert a UTM cluster application of V7.0 into a standalone V7.0 application then you can perform either a cluster update or a node update, but not both. This is due to the fact that KDCUPD is able to transfer data to a newly generated KDCFILE once only.

When you perform a cluster update, you can only transfer data that applies globally to the cluster such as passwords, GSSB, ULS and service-specific data. In the case of a node update, you can only transfer local, node-level data such as TLS, asynchronous messages etc.

1. Use KDCDEF to generate the KDCFILE for the standalone application. To do this, specify OPTION ... GEN=KDCFILE. You must not specify GEN=CLUSTER.

2. Perform either a cluster update or a node update:

   Cluster update

   >	Terminate the UTM cluster application.
   >	Make the old UTM cluster files and the old and new KDCFILE available under the base names specified below. For the old KDCFILE, you can use either the initial KDCFILE or the KDCFILE of a node application. In this case, the KDCFILEs are only used for various checks. The content of the old KDCFILE is not transferred.
   >	Perform the KDCUPD run with the following statements: CLUSTER-FILEBASE OLD=cluster-filebase-old KDCFILE OLD=filebase-old,NEW=filebase-new TRANSFER ... When you do this, KDCUPD transfers the global, cluster-level data such as passwords, locales (BS2000 systems), GSSB, ULS and service-specific data from the UTM cluster files to the KDCFILE of the new standalone application. Explanation cluster-filebase-old             Base name of the old UTM cluster files. KDCUPD transfers the data that applies globally at cluster level to the KDCFILE of the new standalone application. You use the TRANSFER statement to specify the scope of the data to be transferred. filebase-old             Base name of the selected KDCFILE in the UTM cluster application (initial KDCFILE or KDCFILE of a node application). filebase-new            Name of the KDCFILE of the standalone application. KDCUPD transfers the data of the UTM cluster files to the new KDCFILE.

   Node update

   >	Terminate all node applications except for one.
   >	At the node application that is still running, perform an online import for the other node applications in order to be able to transfer as much of the node-specific data as possible.
   >	Terminate this node application.
   >	Perform the KDCUPD run with the following statements: KDCFILE OLD=filebase-old,NEW=filebase-new TRANSFER ... Explanation filebase-old             Name of the KDCFILE of the lastly terminated node application. filebase-new             Name of the KDCFILE of the standalone application. KDCUPD transfers the data from the KDCFILE of the node application to the KDCFILE of the standalone application. You use the TRANSFER statement to specify the scope of the data to be transferred.

3. Start the standalone application with the new KDCFILE.