J06.06 Software Installation and Upgrade Guide

3 Installation, Migration, and Fallback Considerations for
This RVU
See the Readme file and the appropriate softdocs for the latest information on any migration or
configuration steps. Considerations in this chapter are categorized according to the RVU at which
they were introduced.
J06.04
Compiling C++ Programs to Run on RVUs Earlier Than J06.04
Objects compiled by the J06.04 and later C++ compilers might require new functions that are in
the current C++ Common Runtime Library but not in RVUs earlier than J06.04. Specifically, programs
that use either of the following features will fail to load because of unresolved externals (assuming
that they are not linked using the rld_unresolved ignore option):
A try catch block
An exception specifier
To ensure that these programs run correctly on RVUs earlier than J06.04, you must specify the
-WRVU=H06.nn parameter on the c89 command (OSS or PC environment), or the RVU=H06.nn
parameter on the CPPCOMP command (Guardian environment), where nn indicates the RVU on
which the objects will run.
NOTE: The RVU and -WRVU command line parameters do not support J-series RVUs. If J06.03
is the intended target system, specify H06.14.
NOTE: If you are compiling for an H-series target system, nn must be between 08 and 14,
inclusive, as the Runtime Library supports only RVUs H06.08 and later.
You can fix the problem by installing T2831H01^AAD (Common Runtime Library) or later on all
target systems that will run programs generated by the J06.04 or later version of the C++ compiler.
NOTE: You must reboot the system after installing T2831H01^AAD.
SQL/MX Versioning Feature Removed
Certain SQL/MX versioning enhancements that were introduced in an earlier H-series RVU have
been removed in the J06.04 and later RVUs. The following enhancements are no longer supported:
Ability of Expand-connected nodes with compatible SQL/MX versions to interoperate.
Predictable failure on access to or from nodes with incompatible SQL/MX versions.
Ability of each version of SQL/MX to determine compatibility.
CLIM
The CLIM is introduced in the J06.04 RVU. CLIM is a rack-mounted HP ProLiant class server that
provides connectivity between the NonStop host system and either the network or the storage
devices. For CLIM upgrade procedures, see the Cluster I/O Protocols (CIP) Configuration and
Management Manual. For fallback procedures, see Chapter 13.
CLIMs with software associated with J06.04 are not compatible with RVUs of J06.06 and later
RVUs. However, if you are migrating from a J06.04 RVU to a J06.06 or later RVU, the software
upgrade procedures in this manual are ordered so that the CLIM and RVU compatibility is assured
because the RVU on the host is updated first, then, while the processors are halted, the CLIMs are
updated to the CLIM software version associated with this RVU. When the system is loaded, the
CLIM and the NonStop host are at the same level and are therefore compatible.
J06.04 29