HP Integrity NonStop H-Series - Manual (Page 58)

DSM/SCM Interfaces and Tools
DSM/SCM User’s Guide — 529846-014
2 - 15
Using Tools for DSM/SCM Procedures
Using Tools for DSM/SCM Procedures
In addition to the DSM/SCM interfaces, you use these tools during certain DSM/SCM
procedures.
ZPHIRNM Tool
Before you can use new software after you apply a new configuration to a target
system, you must run ZPHIRNM to activate the software. When you apply software to
a target system, DSM/SCM places Guardian files in their destination target
subvolumes (TSVs) with temporary file names; that is, file names that are not the
actual (distribution) product file names used on the target system. The temporary file
names of the new files do not conflict with the file names of currently running programs
that they might replace. ZPHIRNM renames the currently running files to fabricated
names and renames the new files to their real names. ZPHIRNM is a command-line
tool that runs outside the DSM/SCM Pathway environment. For detailed information on
using ZPHIRNM, see
Section 11, Renaming Product Files Using ZPHIRNM .
INITENV Tool
When you receive a new NonStop S-series system or Integrity NonStop system, HP
has already initialized DSM/SCM and set up a default configuration. You can use
INITENV to change some DSM/SCM configuration settings or to reinitialize DSM/SCM
because of a corrupted database.
You must be super ID (255,255) to run INITENV. If you try to perform an INITENV task
that you do not have permission to perform, INITENV stops, and you must restart
INITENV using an appropriate user ID.

When you receive a new system, you run INITENV with the change option to
change a few DSM/SCM configuration settings. See
Task 1: Changing Default
Settings Using INITENV on page 5-3.

To use INITENV to reinitialize DSM/SCM because of a corrupted database or other
problems, see
Reinitializing DSM/SCM on page 5-30.
Starting INITENV
1. Check that DSM/SCM is not running. See Stopping DSM/SCM on page 2-3.
2. Check that you are in the ZDSMSCM volume:
> VOLUME $vol.ZDSMSCM
vol is the volume containing the DSM/SCM TSV.
Note. If you are using multiple logical targets on a system, always run DSM/SCM from the first
ZDSMSCM subvolume installed on the target system, from which INITENV was run, to ensure
that the correct installation files are used. You can also run STOPSCM from the same
ZDSMSCM subvolume if DSM/SCM has finished processing all of its tasks.