DSM Template Services Manual

Installing Templates
DSM Template Services Manual—427187-004
6-3
Task 5: Test the New Templates
> FILE BCDOBJ == Merge templates of subsystem BCD
> EXIT == End of TEMPLI run
The new nonresident template file produced in the example is named NEWNRES.
Task 5: Test the New Templates
Test the new templates before installing them in the system. An installation descriptor
directs EMSTEXT (or the SPI_BUFFER_FORMAT procedures) to use the new
templates with your application. The installation descriptor (=_EMS_TEMPLATES) lets
you specify a new nonresident template file to be accessed for both resident and
nonresident templates. The rest of the system continues to use the current templates.
The installation descriptor that tests the merged templates (including those of
subsystems ABC and BCD) is:
ADD DEFINE =_EMS_TEMPLATES, FILE NEWNRES
Now you can run your application that calls the display-text procedures.
To test operator messages by using a printing distributor, set the installation descriptor
to the new template file to direct the printing distributor to use these templates.
Task 6: Build a System With New Templates
SYSGENR causes new resident and nonresident template files to be created, and it
must know about any new templates to install.
SYSGENR runs TEMPLI as part of its standard operation. As usual, TEMPLI merges a
specified set of template files. SYSGENR determines which files TEMPLI has to merge
from the CONFTEXT file—that is, from this entry in the ALLPROCESSORS paragraph:
FORMATTER_TEMPLATE_FILES template-file-list ;
Separate the file names in template-file-list with commas.
As usual, TEMPLI produces both resident and nonresident template files. These are
work files. SYSGENR places the templates from the new resident template file in
OSIMAGE and places the templates from the nonresident template file in the file
named TEMPLATE in the coldload subvolume.
Building a System With the HP Templates
If you use the installation CONFAUX file, you need enter only the installation descriptor
TANDEM^FORMATTER^TEMPLATE^FILES, which represents the file names of all the
template object files that HP supplies. As an ALLPROCESSORS entry, it looks like:
FORMATTER_TEMPLATE_FILES
TANDEM^FORMATTER^TEMPLATE^FILES ;