DSM/SCM User's Guide

Activating New Software on a Target System
DSM/SCM User’s Guide — 529846-014
10 - 5
Example: Planner Instructions to Operator
Run ZPHIRNM to change the temporary names of the new product files to their
actual names, as explained in Section 11, Renaming Product Files Using
ZPHIRNM.
5. Run merge_whatis if ZPHIRNM indicates it is needed.
If this configuration includes OSS files that DSM/SCM manages and ZPHIRNM
indicates that you need to run merge_whatis after ZPHIRNM finishes, see the
merge_whatis(8) reference page either online or in the Open System Services
Shell and Utilities Reference Manual.
6. Check for $0 EMS messages.
Correct any errors indicated in the $0 EMS messages.
Do not proceed until this step has been successfully
completed.
Check the EMS message log to ensure that all DSM/SCM functions on the target
system finished successfully.
7. If you are not currently running target then a cold load will
be required.
or
Cold load is required.
If the target for which new software is being installed is not the currently running
target, load the system from the SYSnn subvolume for that target in order to run
the new software. The second instruction is included if a system load is required
even though the target is already running.
If you are installing a SUT or other software that required system generation, load
the new operating system. If you made any changes to the CONFTEXT file,
DSM/SCM has run system generation and you must perform system load even if
the software you are installing does not require it.
Note. If you used an OVERRIDE-SYSNN param, you do not need to perform a system
load. See
Managing Software to Avoid a System Load on page 6-2.