DSM Template Services Manual

Installing Templates
DSM Template Services Manual—427187-004
6-8
Central Node Handles Events for All Distributed
Nodes
3. On the central node, run TEMPLI and merge the nonresident template files of the
nodes. Include the nonresident template files of the central node and the nodes
that the central node supports. Use the TEMPLI FILE command and the complete
names of the files, including the node name. For more information, see Task 4:
Build the New Nonresident Template File on page 6-2. For more information on
how TEMPLI merges template files, see How TEMPLI Merges Template Files on
page 5-9.
4. Specify the newly created nonresident EMS template file, using the SCF ALTER
command. For example:
-> ALTER, NONRESIDENT_TEMPLATES $SYSTEM.TEMPLATE.NRTNEW
This change takes effect immediately.
You might need to stop and restart running processes because they might still
have the old nonresident template file open.
5. Confirm the changed EMS template file name with another INFO command:
> SCF INFO SUBSYS $ZZKRN
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. Using COUP to alter the current system template files on HP NonStop K-series
systems, the change does not persist after a SYSGEN and coldload of a newer system image.
However, altering those files using the SCF ALTER SUBSYS $ZZKRN command on an HP
NonStop S-series system is NOT overwritten after a SYSGEN and coldload.
If you use SCF ALTER to specify different template files and later update your system using
DSM/SCM, your system still uses the template files specified in the SCF ALTER command—
not the newly installed template files. To use the new files, issue another SCF ALTER
command specifying the new template files.
Failure to use the most recent template files can create formatting problems for event
messages.