G06.28 Software Installation and Upgrade Guide

Overview of Installing G06.28
G06.28 Software Installation and Upgrade Guide—541688-001
1-44
TMF
upgrading from a pre-G06.20 RVU, back up your HP NonStop TCP/IP configuration
files before running ZPHIRNM. (HP recommends backing up your TCP/IP configuration
files before running ZPHIRNM even if you are on a G06.20 or later RVU.) If you have
to restore information on network services and connections, you will need these files
for the proper network information.
When resuming normal operations after a system load has been performed, you must
have all NonStop TCP/IP configuration files in your $SYSTEM.ZTCPIP subvolume.
Otherwise, applications dependent on proper network connections will fail.
For complete installation instructions, see Back Up (Copy) Files in the
$SYSTEM.ZTCPIP Subvolume on page 10-2 and Update TCP/IP Configuration Files
on page 12-1.
TMF
TMF 3.3 Fallback Issues
Beginning with G06.26, if you do not use any new configurable features after migrating
to TMF 3.3, falling back to the RVU from which you migrated is not a problem. If you
use certain new TMF 3.3 features, however, it is important to first understand how that
impacts subsequent fallback:
If you use the new feature that allows you to add one or more auxiliary audit trails while
TMF is started, it is possible to fall back only to G06.24 or a later RVU. This is because
the TMF audit reading facilities prior to G06.24 cannot handle auxiliary pointer
(AUXPTR) records that specify a variable number of audit trails.
If you issue an ADD AUDITTRAIL AUXnn command while TMF 3.3 is started, the next
AUXPTR record generated contains information for a different number of audit trails
than did the preceding AUXPTR record.
For G06.26 and later TMF 3.3 fallback and migration issues, see the
Interactive Upgrade Guide 2 and the TMF Planning and Configuration Guide.
TMF Migration Considerations for NonStop SQL/MX Release
2.0
If you initially install NonStop SQL/MX Release 2.0, fallback and migration concerns
could apply if you have to fall back to a previous RVU. See the T8607AFH or later
Note.
•
For the DSM/SCM Planner Interface to be operational, the PORTCONF file must have the
correct entry for DSM/SCM. The SERVICES file must have an entry that specifies DSM
and its corresponding port number.
•
Keep your current PROTOCOL file in your $SYSTEM.ZTCPIP subvolume. Update it with
the new lines from the sample PROTOCOL file (SMPLPROT).