H06.25 Software Installation and Upgrade Guide

C/C++ Default Floating-Point Type Change
Beginning in the H-series RVUs, the default floating-point format used by the C/C++ compiler is
changed. In G-series, the default is Tandem floating-point format; on H-Series, the default IEEE
format. The two formats are incompatible; an application must consist of either all Tandem format
modules or all IEEE format modules. Certain HP-supplied libraries use the default IEEE format. If
user programs also use the default format, there is no problem. However, any user program that
explicitly specifies the option to use the Tandem format will encounter a linker error when attempting
to load an HP module that uses IEEE format. The recommended workaround is to compile
applications using IEEE format.
Providers of DLLs should also be aware of this default change, and take steps to provide libraries
that are compatible with both floating-point formats. This can be accomplished in the following
ways:
• Write the library to be floating point neutral
• Provide two versions of the library, one in Tandem format and one in IEEE format.
H06.05
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.05 Release Version Update Compendium and appropriate TMF softdocs.
TS/MP 2.1
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 only 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.
New ACS processes must be started via SCF at system startup and must be managed. These
processes are $ZPnn, $ZLnn, and $ZCSnn.
For details on these issues, see the TS/MP Supplement for Limits Relief.
Fallback
Consult the Global NonStop Solution Center (GNSC) if you have installed TS/MP 2.1 and run
applications that use Pathsend requestors, and then decide to fall back to TS/MP 2.0.
ServerNet Cluster
Starting in H06.05, the HP NonStop ServerNet Switch (model 6780) can support the long-distance
option in a three-zone configuration of the layered topology. Before this RVU, the long-distance
option was restricted to a two-zone configuration. To use the ServerNet cluster long-distance option
H06.05 39