Installation and Upgrade Guide

G06.24 Software Installation and Upgrade Guide—528593-005
10-1
10 Running ZPHIRNM
During the Build/Apply phase, DSM/SCM places product files in their subvolumes with
temporary (fabricated) file names so that the new file names do not conflict with the file
names of currently running programs.
This section 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 the 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.
Alerts
•
If you are upgrading to the G06.24 RVU, back up copies of TCP/IP configuration
files in the ZTCPIP subvolume before running ZPHIRNM. (See Back Up (Copy)
Files in the $SYSTEM.ZTCPIP Subvolume on page 10-2.)
•
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.