An offline update in a UTM cluster application is necessary in the following cases:
If you convert the UTM cluster application from a previous version to V7.0.In this case you must also regenerate the UTM cluster files (OPTION GEN=(CLUSTER, KDCFILE), see "Offline Update with cluster update".
If you make adaptations which are listed in section "Adaptations to the UTM generation that require an offline update". For most changes, it is sufficient simply to recreate the KDCFILE (OPTION GEN=KDCFILE). However, in the case of certain adaptations it is also necessary to regenerate the UTM cluster files (OPTION GEN=(CLUSTER, KDCFILE)).
In order to perform an offline update, it is necessary to shut down all the node applications and therefore also the UTM cluster application for at least a short period.
In general, the following applies: When a node application is started, the KDCFILE must not be older than the UTM cluster files.
If you perform a conversion from a previous version to V7.0 then you must install openUTM V7.0 on all the nodes before calling KDCDEF.
Adaptations to the UTM generation that require an offline update
The table below indicates what you have to specify in the OPTION statement for the individual changes.
Type of change | KDCDEF control | OPTION GEN= |
|---|---|---|
Switching between operation with and without users | USER | (CLUSTER,KDCFILE) |
Switching between operation with and without multiple sign-on being permitted | SIGNON | KDCFILE |
Switching between applications with and without a formatting system | FORMSYS | (CLUSTER,KDCFILE) |
Changing the password history | SIGNON | KDCFILE |
Changing the database systems | DATABASE, RMXA | (CLUSTER,KDCFILE) |
Changing the number of LSSBs, GSSBs or ULSs | MAX LSSB, | (CLUSTER,KDCFILE) |
Reduction in the maximum number of services that the user is permitted to stack | MAX NRCONV | KDCFILE |
Reduction in the maximum number of asynchronous services that can be opened simultaneously | MAX ASYNTASKS, | KDCFILE |
Reduction in the size of the node page pool | MAX PGPOOL, | KDCFILE |
Reduction in the size of the process-specific buffer for caching restart data | MAX RECBUF, | KDCFILE |
Changing the length of the communication area | MAX KB | (CLUSTER,KDCFILE) |
Reduction in the size of the standard primary working area | MAX SPAB | KDCFILE |
Changing the size of the message area | MAX NB | (CLUSTER,KDCFILE) |
Changing the maximum length of physical output messages | MAX TRMSGLTH | (CLUSTER,KDCFILE) |
Reduction of the maximum length of the user data in LPUT records | MAX LPUTLTH | KDCFILE |
Switching between UTM-S and UTM-F | MAX APPLIMODE | (CLUSTER,KDCFILE) |
Increasing the number of the generated node applications | CLUSTER-NODE | (CLUSTER,KDCFILE) |
Changing the names of the ULSs | ULS | (CLUSTER,KDCFILE) |
Reducing the size of the cluster pagepool | CLUSTER PGPOOL, | (CLUSTER,KDCFILE) |
Changing the number of the cluster pagepool files | CLUSTER | (CLUSTER,KDCFILE) |
All other changes in the CLUSTER statement except for the PGPOOL parameter | CLUSTER | (CLUSTER,KDCFILE) |
Offline Update with cluster update
Proceed as follows:
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 the online inverse KDCDEF, otherwise the update generation is not correct.Terminate the UTM cluster application.
Create generation statements for new objects manually or modify existing generation statements to suit your requirements.
Generate a new initial KDCFILE and new cluster files using the modified KDCDEF statements. When you do this, specify GEN=(CLUSTER, KDCFILE) in the KDCDEF statement OPTION, see "OPTION - manage the KDCDEF run".
Make the old and new UTM cluster files as well as an old KDCFILE and the new initial KDCFILE available. You may need to rename the files first.
Use KDCUPD to perform a cluster update. This transfers user data from the UTM cluster application run to the new UTM cluster files. This data includes, for example, GSSB, ULS, the service data of users with RESTART=YES as well as the passwords of users.
For the old and new KDCFILE, you can use either an initial KDCFILE or a KDCFILE of a node application. For this KDCUPD run, the KDCFILEs are used only for the program run and for a variety of checks. The content of the old KDCFILE is not transferred and the new KDCFILE is not changed.
Perform the KDCUPD run with the following statements:
CLUSTER-FILEBASE OLD=cluster-filebase-old,NEW=cluster-filebase-new KDCFILE OLD=filebase-old,NEW=filebase-new TRANSFER ...
Explanation
cluster-filebase-old
Base name of the old UTM cluster files.
cluster-filebase-new
Base name of the new UTM cluster files generated by KDCDEF. KDCUPD transfers the data that is valid globally in the cluster from the old UTM cluster files to the new UTM cluster files. You use the TRANSFER statement to specify the scope of the data to be transferred.
filebase-old
Base name of an old KDCFILE in the UTM cluster application.
filebase-new
Base name of a new KDCFILE in the UTM cluster application.
Copy the new initial KDCFILE (see step 5) into the node-specific filebase for a node application.
Perform a KDCUPD run for this node application (node update) 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 ...During this run, transfer all the user data from the last application run of this node application into the new KDCFILE of this node application. This allows, for instance, asynchronous messages of this node application to be transferred from the old KDCFILE to the new KDCFILE.
Carry out steps 7 and 8 for all other node applications without delay in order to update all node applications to the same generation status.
Restart he UTM cluster application.
Offline Update without cluster update
If you make only such changes that are listed in the table on "Offline update of a UTM cluster application" and which have the entry KDCFILE in the column OPTION GEN= then you proceed as follows:
> | Carry out steps 1 through 4 starting on "Offline update of a UTM cluster application". |
> | In step 5, generate a new initial KDCFILE using the modified KDCDEF statements. When you do this, specify GEN=KDCFILE in the KDCDEF statement OPTION, you must not specify GEN=CLUSTER! |
> | Carry out steps 7 through 10 on "Offline update of a UTM cluster application". |
Special features in UTM-F cluster applications
In UTM cluster applications, the global UTM storage areas GSSB and ULS are also transaction-oriented in the case of UTM-F. The service data belonging to a user is saved when the user signs off.
This means that in the case of an update generation with a cluster update, it is possible to transfer the same data as in the case of a UTM-S cluster application.