H06.27 Software Installation and Upgrade Guide

8 Running ZPHIRNM
During the Build/Apply phase, DSM/SCM places product files in their subvolumes with temporary
(fabricated) file names so that new file names do not conflict with the file names of currently running
programs.
This chapter describes how to run the ZPHIRNM program on the target system to:
• Rename the files that currently have actual file names with fabricated names. These files become
obsolete when the new files are renamed.
• Rename new files, which have fabricated names, with their actual names.
Warning, error, and completion messages are written to a log file if you choose to create one.
Error and completion messages are also displayed in the terminal-emulation window.
After ZPHIRNM has completed renaming all OSS and Guardian files, it will run ZMODGP if it
exists in the SYSnn being activated and if:
• The configuration being activated contains a ZCNFDEFS TSV:
104 Processing TSV $SYSTEM.ZCNFDEFS Mapfile ZMP0007N (102)
• One or more of the ZcccGP files in the ZCNFDEFS TSV are new or changed (as compared
to the last configuration activated). If none of the ZcccGP files change, ZMODGP is not run.
Alerts
• Back up copies of HP NonStop TCP/IP configuration files in the ZTCPIP subvolume before
running ZPHIRNM.
• Applications that use files that are being replaced should not be running. To avoid any
possibility of conflict, stop all applications, except for the TMF subsystem, before running
ZPHIRNM.
• You must have rename (purge) access to all files being renamed. Run ZPHIRNM as the super
ID (255,255).
• If you are connected to an Expand network, you might see a message stating that the NonStop
SQL file, ZZSQLCI2, was not renamed during ZPHIRNM. However, on further examination
of the log file, you might find that ZPHIRNM did finally rename the file, in which case you
can ignore the error message and continue.
• If you are using DSM/SCM to manage OSS files, ZPHIRNM notifies you if and when to run
the merge_whatis command. Run merge_whatis after loading the new system.
• If ZPHIRNM is run in PREVIEW mode, ZMODGP is run in TRIAL mode. However, any errors
in the new and changed files will not be discovered in preview or trial mode because ZPHIRNM
in preview mode does not actually rename the files. Therefore, ZMODGP will not be run
against the same files as when the real file activation is done.
• Prior to performing an RVU migration to this RVU, install DSMSCM SPR T6031H02^ACJ or
later. See “DSM/SCM Upgrade Issues/Interoperability SPR Requirements” (page 59) for more
information.
Back Up (Copy) Files in the $SYSTEM.ZTCPIP Subvolume (Best Practice)
Make backup copies of these files in the $SYSTEM.ZTCPIP subvolume before running ZPHIRNM,
which overwrites them with sample versions.
110 Running ZPHIRNM