H06.12 Software Installation and Upgrade Guide

6. To confirm that the Build and Apply tasks finish successfully and that a snapshot has been
received into the host database, wait until the status shows that all requests are complete.
7. Select Window>Refresh.
The Configurations Revision dialog box is refreshed and shows the new software
configuration revision containing the H02 DSM/SCM SPR.
Rename the Applied DSM/SCM H02 Files By Running ZPHIRNM
1. Stop DSM/SCM:
> VOLUME $dsmscm_vol.ZDSMSCM
> RUN STOPSCM
where $dsmscm_vol is the DSM/SCM volume.
2. Run ZPHIRNM:
> RUN ZPHIRNM $volume.SYSnn
where SYSnn is the current SYSnn (because no SYSGEN or system load is required).
3. When asked if you want to use a log file with the session, enter Y.
4. When prompted, enter a file name for the log file.
ZPHIRNM displays this message:
Log file, filename, was successfully created.
ZPHIRNM processes the file renaming.
5. Verify that ZPHIRNM ran successfully by reviewing the specified log file. For an example
of output, “ZPHIRNM” (page 93).
Run the INSTALL^TEMPLATES Macro
EMS templates are used by EMS to format EMS messages. After running ZPHIRNM, and if
notified to do so by DSM/SCM, run the INSTALL^TEMPLATES TACL macro to install DSM/SCM
EMS templates in their proper locations.
NOTE: The files newres and newnres are used as temporary names until the next SYSGEN
and system load.
The INSTALL^TEMPLATES macro is located in the $SYSTEM.ZINSAIDS subvolume and invokes
the TEMPLI program to build new resident and nonresident EMS template files.
You must be logged on as a super.super (255, 255) user to run the INSTALL^TEMPLATES macro.
This macro cannot be run with the NOWAIT option and takes approximately ten minutes to
finish.
For detailed instructions on running the INSTALL^TEMPLATES macro, including troubleshooting
information, see “If Running INSTALL^TEMPLATES Is Required” (page 127).
Restart Applications
You can now start your application software. Follow your site’s procedures for executing the
system configuration and startup (command) files to accomplish this.
DSM/SCM is often started automatically by a system command file. If not, you must start
DSM/SCM manually as described next.
Before Starting DSM/SCM
1. Check that TMF is started:
136 Installing SWID, DSM/SCM PVU, and Planner Interface (PI) Client Software