H06.15 Software Installation and Upgrade Guide

Migrating From TS/MP 2.0
After the system image is built using TS/MP 2.3, TS/MP 2.0 users need to remove #ROUT from
Persistent Manager ($ZZKRN) and configure #ZACS before starting TS/MP 2.3
Migrating From TS/MP 2.1
If you ordered and received TS/MP 2.1 on a prior H-series RVU, you will automatically receive
TS/MP 2.3 instead of TS/MP 2.1 when you receive an H06.14 or later SUT.
H06.15
Compiling C++ Programs to Run on RVUs Earlier Than H06.15
Objects compiled by the H06.15 and later C++ compilers might require new functions that are in
the current C++ Common Runtime Library but not in RVUs earlier than H06.15. 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 H06.15, 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: 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 H06.15 or later version of the C++ compiler.
NOTE: You must reboot the system after installing T2831H01^AAD.
SQL/MX Versioning Feature Removed
The SQL/MX versioning enhancements that were introduced in the H06.13 RVU have been removed.
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.
54 Installation, Migration, and Fallback Considerations