Installing Job Management Manager › Backup of Files from a Previous Installation › Preserving customized startup files

Preserving customized startup files

The installation procedure removes the definitions of all customizable logical names from the main manager startup procedure to new user customizable files in the directory NSCHED$COM. User customizable files include all customizable logical names, even those which were not previously included in the startup file.

System specific logical names are placed in the file NSCHED$COM:UJM$MANAGER$STARTUP_nodename.COM where nodename is the name of the local system. Cluster-wide logical names are placed in the file NSCHED$COM:UJM$MANAGER$STARTUP_SYSCLUSTER.COM. If a logical name is defined in both the system table and in the cluster table, only the value in the system table is preserved.

The startup procedure SYS$STARTUP:UJM$MANAGER$STARTUP.COM will run these two files if they are present.

Job Management Manager logical names which are defined in LNM$SYSTEM_TABLE at the time of product installation are provided in the system specific custom startup file; logical names found in LNM$SYSCLUSTER_TABLE are provided in the cluster common custom startup file. Any logical name present in the template file but not defined in any of the above mentioned LNM tables is copied as is (commented out) to the system specific custom file, along with related comments. The operator can review and amend these definitions by editing the custom file.

Upon upgrade, the installation procedure detects and saves any existing application startup file that might have been customized. The following table summarizes the files that are saved, where from, and where to. The last column indicates what happens to the original file, at the end of the installation.

Notes:

• When the installation procedure backs up a file, the name is changed; the characters _yyyymmdd are appended to each file name. This represents the last modification date of the file being backed up.
• The files that are valid for the current release are backed up to NSCHED$COM:. Any legacy files that are not to be reused for the current release are backed up to NSCHED$DATA:
• The startup template file UJM$MANAGER$STARTUP_LOCAL.TEMPLATE is placed in NSCHED$COM: for future reference.