H06.26 Release Version Update Compendium

Interoperability
SQL/MX 3.2.1 interoperates with SQL/MX 3.2.
NSJ 7.0 support
SPJ, JDBC/MX T2 (32-bit, 64-bit), and T4 drivers require NSJ7.0.
• JDBC/MX T2 Driver
T1275 (JDBC Type 2 Driver)◦
◦ Pax file location: $SYSTEM.ZOSSUTL
◦ Filename: T1275PAX
• JDBC/MX T4 Driver
T1249 (JDBC Type 4 Driver)◦
◦ Tar file location: $SYSTEM.ZMXODBC
◦ Filename: T1249TAR
NOTE: The upgrade will not affect the standard RVU Installation procedure.
Migration Considerations
• Migration from the previous RVU to the next RVU (which includes these features) does not
require customer changes to applications, system management scripts or procedures.
• The procedure to upgrade to SQL/MX Release 3.2.1 from SQL/MX Release 2.3.4 is the same
as upgrade to 3.0 or 3.1 or 3.2 from SQL/MX Release 2.3.4.
• Metadata upgrade is optional if there are no new database features to be used for the existing
schemas.
• You can reuse the MFC module files while upgrading from SQL/MX 3.2 to 3.2.1.
• The embedded SQL module files must be recreated or recompiled while upgrading from
SQL/MX 2.3.x to 3.x.
• In SQL/MX Release 2.3.x, the format of the CPU lists stored in the ODBC/MX metadata is
different from the format of the CPU lists stored in SQL/MX Release 3.2.x, and this format is
not recognized in SQL/MX Release 3.2.x. Starting with SQL/MX Release 3.2, mxtool includes
the fixmxcsmd option. The fixmxcsmd option supports the conversion of the SQL/MX Release
2.3.x CPU list format to the SQL/MX Release 3.2.x CPU list format in the
ENVIRONMENTVALUES MXCS metadata table.
• Installation of NSJ7 does not automatically create the softlink /usr/tandem/java. If you
have migrated all the applications to NSJ7.0, HP recommends you create a softlink manually
to point to the NSJ7 JDK/JRE installation (/usr/tandem/nssjava/jdk170_h70). Create
the softlink /usr/tandem/java to point to the NSJ7 home directory as follows:
$ ln -s /usr/tandem/nssjava/jdk170_h70 /usr/tandem/java
After creating this softlink, applications may fail if they have not been migrated to NSJ7.
Fallback Considerations
Fallback from the RVU that includes these features to the previous RVU shall not require customer
changes to applications or system management scripts or procedures, if you have not used any
new limits or features.
SQL/MX Release 3.2.1 13