H06.27 Software Installation and Upgrade Guide

12 Running ZPHIRNM to Reactivate the Previous Software
Revision
Fallback Considerations for NonStop Software Essentials After ZPHIRNM
If after migrating to this RVU, you decide to fall back to an RVU earlier than H06.24, you need to
be aware of the fallback considerations for NonStop Software Essentials. NonStop Software
Essentials 2.0 or later components are not compatible with NonStop Software Essentials 1.0
components.
When you fall back, the ZPHIRNM step may rename the files in $SYSTEM.ZNSE, and you might
not be able to continue using NonStopSoftware Essentials after reloading the system. These are
the possible fallback scenarios you might encounter:
• If the T0894H02 or later server was already installed on the fallback RVU, there should be
no problems.
• If the T0894H01 server was installed on the fallback RVU, you can either revert to using the
T0895V01 client from another CMS, or preferably you can install the T0894H02 or later
server and T0884V02 client as described in the Nonstop Software Essentials Installation and
Quick Start Guide.
• If no version of NonStop Software Essentials was installed on the fallback RVU, you can either
revert to using the DSM/SCM Planner Interface, or you can install the T0894H02 or later
server manually as described in the Nonstop Software Essentials Installation and Quick Start
Guide.
Alerts
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. You can ensure this access
by running 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 may find that ZPHIRNM did finally rename the file, in which case you can
ignore the error message and continue.
• Make sure that you drain the Spooler before running ZPHIRNM. If you drain the Spooler after
running ZPHIRNM, an error message appears indicating that the spooler program and library
versions are different, and the Spooler terminates with errors.
Drain the Spooler (Optional)
Before executing the SPOOLCOM;SPOOLER,DRAIN command:
• Use the SPOOLCOM;COLLECT $collector-process, LISTOPENS command to identify
processes that currently have jobs open.
• Use the SPOOLCOM;JOB (STATE PRINT) command to determine which jobs are currently
printing.
• Take the appropriate action to ensure that these jobs either terminate when finished or are
stopped.
• Drain the Spooler. To drain the Spooler, log on as a super group user (255,n), access
SPOOLCOM, and enter the following command:
138 Running ZPHIRNM to Reactivate the Previous Software Revision