DSM Template Services Manual

Introduction
DSM Template Services Manual—427187-004
1-12
Replacing Templates on a Running System (Using
COUP)
2. View the current EMS template file names (shown here in bold type) with an INFO
command:
-> ASSUME SUBSYS $ZZKRN
-> INFO
3. Change the configuration, using the ALTER command to specify different files for
the resident and nonresident EMS templates. For example:
-> ALTER, RESIDENT_TEMPLATES $SYSTEM.TEMPLATE.TNEW,
NONRESIDENT_TEMPLATES $SYSTEM.TEMPLATE.NRTNEW
These changes take effect immediately.
4. Confirm the changed EMS template file names with another INFO command.
To reverse this operation, repeat the ALTER command with the original values.
Replacing Templates on a Running System (Using COUP)
If you perform normal system software installation (which includes running the
INSTALL^TEMPLATES macro on a DSM/SCM target system), this procedure is not
necessary. Otherwise, to specify the template object files for the Event Management
Service (EMS) to use on a system running a D-series RVU:
1. Set the default object type to ALLPROCESSORS for subsequent COUP command
(see the Dynamic System Configuration Manual ):
1)ASSUME ALLPROCESSORS
NONSTOP KERNEL - Info SUBSYS \EAST.$ZZKRN
Current Settings
*DAYLIGHT_SAVING_TIME ................ USA66
*NONRESIDENT_TEMPLATES................ $SYSTEM.SYSTEM.TEMPLATE
*POWERFAIL_DELAY_TIME................. 30
*RESIDENT_TEMPLATES................... $SYSTEM.SYSTEM.RTMPLATE
SUPER_SUPER_IS_UNDENIABLE............ OFF
*SYSTEM_NAME.......................... \EAST
*SYSTEM_NUMBER........................ 254
SYSTEM_PROCESSOR_TYPE ............... NSR-W
*TIME_ZONE_OFFSET..................... -8:00
Caution. Specifying different template files using the SCF ALTER command is not overwritten
after a SYSGEN and coldload.
For example, if you use SCF ALTER now to specify different files, when you later update your
system using DSM/SCM, your system still uses the template files specified in your SCF ALTER
command—not the new files in the newly installed update. In this case, you must use SCF
ALTER again to specify the new files.
Failure to use the most recent template files can create formatting problems for event
messages.