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

10 Renaming Product Files Using ZPHIRNM
When you apply software to a target system, DSM/SCM places the product files in their destination
TSVs with temporary file names so the new files do not conflict with the file names of currently
running programs on the target system. Before you can use the new software you applied, run
ZPHIRNM to rename the files that currently have actual file names. These files are renamed to the
fabricated names and become available only in the case of a backout. ZPHIRNM also renames
the new files from the fabricated names to their actual names. The ZPHIRNM log file is an edit file.
Statistical information appears at the end of a ZPHIRNM run.
Topics discussed in this section include:
• “Prepare to Run ZPHIRNM” (page 123)
• “Run ZPHIRNM in Preview Mode” (page 123)
• “Run ZPHIRNM” (page 124)
• “Error Handling” (page 125)
To rename product files for a Clone Group, use the CLONE utility to run ZPHIRNM. See “Renaming
Product Files for a Clone Group” (page 177) .
Prepare to Run ZPHIRNM
1. Log on to the target system as the super ID (255,255) or any user who has rename (purge)
access to all files being renamed.
2. Make sure any software that is being replaced, or that uses files being replaced, is not active.
(The operator instructions should tell you to stop all applications before running ZPHIRNM.)
To avoid any possibility of conflict, stop all applications currently running on the target system
until after ZPHIRNM finishes.
NOTE: For some software revisions, you must leave certain applications running, such as
TMF or Safeguard. ZPHIRNM in PREVIEW mode displays a message if TMF must be running
to rename certain files.
3. Check that you are in the ZDSMSCM subvolume:
> VOLUME $vol.ZDSMSCM
where vol is the volume containing the DSM/SCM TSV.
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.
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.
4. Stop DSM/SCM on the target system. For more information, see “Stopping DSM/SCM”
(page 39) .
Run ZPHIRNM in Preview Mode
HP highly recommends running ZPHIRNM in preview mode before running ZPHIRNM to actually
change the file names. Preview mode simulates the ZPHIRNM process without updating files or
activating the configuration. This allows you to evaluate, correct, and interactively test any errors
detected without affecting your system, ensuring a successful configuration activation.
Prepare to Run ZPHIRNM 123