H06.12 Software Installation and Upgrade Guide

Previously, three SANMAN Event Management Service (EMS) events that called out a modular
ServerNet expansion board (MSEB) explicitly for S-series have been modified to report a more
generic text message.
Before an Integrity NonStop NS-series server node can be connected to an existing NonStop
ServerNet Cluster with S-series nodes, an upgrade to SNETMON SPR T0294AAP is required on
all S-series nodes if these nodes are not already running the minimum required T0294AAP SPR
or a subsequent SPR. Failure to install the minimum T0294AAP SPR on the S-series nodes prevents
those nodes from successfully discovering Integrity NonStop NS-series server nodes and
vice-versa, thereby preventing the establishment of Expand-over-ServerNet lines between S-series
and H-series server nodes.
T0294AAP can be installed online and does not require a system load.
Remote Database Facility (RDF)
In order to replicate the NonStop Remote Database Facility (RDF, T0346) software from an S-series
system to an NS-series system, the S-series system must be on the T034A06^AAB or later version
of RDF.
HP Tandem Failure Data System (TFDS)
HP Tandem Failure Data System (TFDS) is available on the NonStop Series TNS/E platform and
provides hardware, software, and subsystem failure analysis and automated processor reload
and dump capabilities.
• For Integrity NonStop NS-series servers, TFDSCOM commands have been introduced,
existing commands have been modified, and some commands have been eliminated. For
example, the fast memory dump (FMD) that is ON by default in G06.nn RVUs is not available
on TNS/E platforms.
• For new tokens and messages, EMS templates are adapted for Integrity NonStop NS-series
servers.
For more information on new commands and options, see the Interactive Upgrade Guide 2, and
the TFDS Programmer’s Guide.
TMF 3.3
The HP NonStop Transaction Management Facility (TMF) 3.3 was introduced in the H06.05 RVU.
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 the new TMF 3.3 feature that allows
you to add auxiliary audit trails while TMF is started, however, you must first understand how
that impacts any subsequent fallback. For H06.11 and later TMF 3.3 fallback and migration issues,
see the TMF Planning and Configuration Guide.
The products T8697 (the older product version update of ARLIB) and T8923 (TIFSERVE) are not
included in H-series RVUs. T8697 is being replaced by T2781 (ARLIB2). For more information,
see the H06.12 Release Version Update Compendium and appropriate TMF softdocs.
TS/MP 2.1
The HP NonStop TS/MP 2.1 was introduced in the H06.05 RVU. TS/MP 2.1 provides Pathsend
users with higher link capacity to client processes. TS/MP 2.1 is intended solely for Pathsend
users using TS/MP 2.0. It does not apply to SCOBOL users or TS/MP 3.0 users.
Migration
In general, all TS/MP 2.0 applications that use Pathsend requestors and TS/MP 2.0 scripts (also
called OBEY files) can run in a TS/MP 2.1 environment. However, you might need to modify the
PATHMON process configuration to achieve optimum TS/MP 2.1 performance.
Remote Database Facility (RDF) 49