An update generation of the KDCFILE for UTM cluster application will be necessary, for instance, if spare capacity for dynamic objects has been exhausted or if changes must be made to the configuration that are not possible using the dynamic administration facilities. Examples include entering additional transport system end points or partner applications for distributed processing or increasing the size of the cache, or page pool.
If you modify the KDCFILE without terminating the UTM cluster application then you must not change the order of the TAC statements. Otherwise services may be terminated abnormally on service restarts. As a result, you must append new TAC statements at the end and must not delete any TAC statements.You should also not modify the RESTART parameter in the USER statements.
Proceed as follows to perform an update generation of the KDCFILE:
Use the administration facilities to delete all objects that can be dynamically administered and that are no longer to be included in the new configuration.
Create the generation statements for a new KDCDEF run as follows: First create the statements for new objects that have been newly introduced into the application dynamically. To do this, call the online inverse KDCDEF in an active node application.
Note that you must not create, delete or modify any more objects after you have performed an online inverse KDCDEF, otherwise the update UTM generation will not be correct.Create generation statements for new objects manually or modify existing generation statements to suit your requirements.
When generating the new KDCFILE, specify the filebase name of the cluster user file currently opened by the running openUTM application under CLUSTER USER-FILEBASE=, see "CLUSTER - Define global properties of a UTM cluster application".
Generate a new initial KDCFILE using the modified KDCDEF statements. To do this specify OPTION GEN=KDCFILE. You must not specify GEN=CLUSTER!.
Terminate one of the node applications normally (e.g. using KDCSHUT GRACE or WinAdmin/WebAdmin).
Rename the KDCFILE of the terminated node application (in preparation for the KDCUPD run).
Copy the new initial KDCFILE created in step 4 into the node-specific filebase for the terminated node application from step 6.
Perform a KDCUPD run for this node application using the KDCFILE of this node as the new KDCFILE (node update).
When you do this, specify the following KDCUPD statements:
KDCFILE OLD=filebase-old,NEW=filebase-new
TRANSFER ...Explanation
filebase-old
Base name of the node application’s old KDCFILE.filebase-new
Base name of the new KDCFILE generated using KDCDEF and copied for the node application.KDCUPD transfers the data from the old KDCFILE to the node application’s new KDCFILE. You use the TRANSFER statement to specify the scope of the data to be transferred. This allows, for instance, asynchronous messages of this node application to be transferred from the old KDCFILE to the new KDCFILE.
Restart this node application using the new KDCFILE that has been prepared as described.
When you restart the node application, the values of the start parameters that apply globally in the cluster are taken over from the running UTM cluster application. The sources for these are as follows:
the administration journal in which recent global administration actions are logged,
the file containing the online copy of the management data of the UTM cluster application from which older changes are taken over.
Carry out steps 5 through 9 for all other node applications without delay in order to update all node applications to the same generation status.
- Note that global administration of all applications of a cluster and an online inverse KDCDEF run are not possible until all active node applications have been updated to the same generation status. Local administration of individual node applications, however, can be carried out at any time.
After a node application has been restarted on the basis of a newly generated KDCFILE, it is not possible to start other node applications using a KDCFILE from an older generation run.