DSM/SCM User's Guide

Activating New Software on a Target System
DSM/SCM User’s Guide — 529846-014
10 - 6
Example: Planner Instructions to Operator
8. RUN INSTALL^TEMPLATES to update EMS template files.
EMS templates format EMS messages. The Run INSTALL^TEMPLATE instruction
is generated only on the basis of product files present in the software configuration.
If you change the software configuration to include products that force system
generation, DSM/SCM directs a system generation program to run TEMPLI,
ensuring installation of the user template specified in the CONFTEXT file.
To run the INSTALL^TEMPLATES program to install the EMS templates in their
proper locations:
a. Set the volume and subvolume to $SYSTEM.ZINSAIDS.
b. Load the TACLMACS file.
c. Enter the command INSTALL^TEMPLATES.
9. DOWN/STOP any DEVICE/LINE using filename.
Use SCF to STOP these DEVICES/LINES, and then to start them
again.
product number product name includes IOP OBJECT code changes.
If one or more input/output processes (IOP) files change in this configuration
revision but does not require system generation and one or more (IOPs) have
changed, use SCF to:
a. Stop all devices and lines that use the IOP file.
b. Restart the devices and lines to put the new IOP file into effect. For more
information, r
efer to the SCF Reference Manual for G-Series RVUs or SCF
Reference Manual for J and H-Series RVU.
10.Restart all applications.
Use the TI to complete any necessary DSM/SCM activities.
The last step in activating the new software is to restart all the applications you
stopped in Step 1.
Note. DSM/SCM decides whether a system generation program should run TEMPLI
based on the product files in the software configuration on which Build/Apply is performed.
If you add the user template to the CONFTEXT file but keep the same configuration,
DSM/SCM does not run TEMPLI through system generation or generate the operator
instruction Run INSTALL^TEMPLATE. As a result, the user template is not installed.