DSM Template Services Manual

Introduction
DSM Template Services Manual—427187-004
1-13
Installing Templates by Using SYSGENR
2. Change the configuration using the ALTER command to specify different files for
the resident and nonresident EMS templates. For example:
2)ALTER EMS^TEMPLATES (RESIDENT newresident, NONRESIDENT
newnonres)
where newresident is the name of the resident file to be installed and
newnonres is the name of the nonresident file to be installed.
3. Confirm the changed EMS template file names with the INFO command:
3)INFO
To reverse this command, repeat the ALTER command with the original values.
Installing Templates by Using SYSGENR
1. Modify the SYSGENR CONFTEXT configuration file.
Make sure the FORMATTER_TEMPLATE_FILES statement in the
ALLPROCESSORS paragraph includes the template object files for both HP and
user-written applications.
2. Run DSM/SCM, which automatically runs SYSGENR.
SYSGENR installs the resident and nonresident templates. SYSGENR
automatically runs TEMPLI, generating the resident and nonresident template files
from the template object files specified in the CONFTEXT file. The resident
template file is installed into the operating system image (OSIMAGE), and the
nonresident template file is stored in the coldload subvolume.
For a detailed description of the entire installation process, see Section 6, Installing
Templates.
Using Templates
Once templates are installed on a system, the EMSTEXT and SPI_BUFFER_FORMAT
procedures can access the templates to create display text.
How Template Services Handles
ZEMS-TKN-TEXT Tokens
The EMS primary collector ($0) converts pre-EMS, unnumbered console messages to
event messages containing a ZEMS-TKN-TEXT token. The TEXT token contains the
operator message as a text string.
Note. To test your templates before installing them on the system, set the
=_EMS_TEMPLATES DEFINE. This DEFINE can direct applications to use a particular
nonresident template file instead of the resident and nonresident template files installed on
the system.