G06.30 Software Installation and Upgrade Guide

G06.30 Software Installation and Upgrade Guide—543764-002
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 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 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.
ZPHIRNM copies a new dial-out report SWCONFIG from SYSnn being activated to
ZDSMSCM subvolume. ZPHIRNM updates the SWCONFIG report with the date and
time of activation and generates a TSM (or OSM) software configuration incident
report. In the PREVIEW mode, ZPHIRNM does not perform any dial-out related
activities.
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
•
If you are upgrading to the G06.30 RVU, back up copies of NonStop 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.