Before you start your work, please read the following notes:
When you create the new KDCFILE with KDCDEF, you must ensure that you do not accidentally overwrite the old KDCFILE and thus destroy important application data!
The records in user log files (USLOG files) must be saved before the application is restarted because openUTM overwrites the current USLOG file generation from the beginning after a KDCUPD run.
There are a number of ways of avoiding overwriting the KDCFILE:
As shown here, you create the new KDCFILE before terminating the application. You use the same base name, but set up the KDCFILE under another ID (BS2000 systems) or in another directory (Unix, Linux and Windows systems). After you terminate the application, you must rename or copy the files for the subsequent KDCUPD run.
First terminate the application and then rename the old KDCFILE and all associated files by changing the base name. Alternatively, copy the old KDCFILE and all associated files to a different ID (BS2000 systems) or to a different directory (Unix, Linux and Windows systems). Then start the KDCDEF run to generate the new KDCFILE with the same base name.
Specify the following in the subsequent KDCUPD run:KDCFILE OLD= base_name-renamed/copied-KDCFILE
KDCFILE NEW= base_name-new-KDCFILE
Use a new base name for the new KDCFILE and work with this name in the KDCUPD run. When you subsequently start the application, you can either use the new base name or continue to use the previous base name after copying and renaming the files.