DSM Template Services Manual

Installing Templates
DSM Template Services Manual—427187-004
6-4
Installing Modified HP Templates
Building a System That Includes Your Templates
To add templates for your own applications, append the file names of the template
object files to template-file-list. For instance, adding templates for your
subsystems ABC and BCD to those from HP (as represented by the installation
descriptor) makes the entry in the ALLPROCESSORS paragraph look like:
FORMATTER_TEMPLATE_FILES
TANDEM^FORMATTER^TEMPLATE^FILES, ABC, BCD ;
After the SYSGENR run, the resident templates for subsystem ABC and BCD are in
OSIMAGE. The nonresident templates are in the file named TEMPLATE in the cold-
load subvolume.
To install a user-written template using DSM/SCM, refer to the DSM/SCM User’s
Guide.
Installing Modified HP Templates
To help you customize how event messages are displayed, HP provides the template
source and object files for most HP NonStop™ OS subsystems and management
applications, and the DDL definition files needed for template compilation.
Modifying and installing HP templates is mostly identical to creating and installing your
own application templates. For instance, building DDL dictionaries and compilation are
the same. In addition, you can use the same installation descriptor to test templates
and can use SCF, TEMPLI, and SYSGENR in the same way. For details, see Installing
Templates for a New Application on page 6-1.
Names and Locations of HP Files
This subsection describes the names of files that HP supplies for NonStop servers.
Template Source and Object Files
Template related files are in subvolume $vol.ZTEMPL. $vol, the volume on which the
ZTEMPL ISV was installed, depends on your site. By default, $vol is the volume to
which the SUT was restored.
Template source files are named as:
•
$vol.ZTEMPL.SxxxTMPL are the template source files.
•
$vol.ZTEMPL.ZxxxTMPL are the template object files.
In both cases, xxx is the three-letter abbreviation for the application; for example,
COM, EMS, or SPI.
Although HP supplies most of its template source files, some files are omitted because
they are not subject to customization. Therefore some ZTEMPL.ZyyyTMPL files have
no ZTEMPL.SyyyTMPL counterpart (for an application yyy).