J06.14 Release Version Update Compendium

Support for 64-bit applications using 64-bit driver
NonStop OSS ODBC/MX now supports 64-bit applications using a 64-bit driver.
Migration Considerations
IMPORTANT: Before installing J06.14, see the instructions in Hotstuff HS03173. For details on
how to access Hotstuff messages, see “ExpressNotice” (page 24).
• 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. However,
you must recompile your applications.
• The procedure to upgrade to SQL/MX Release 3.2 from SQL/MX Release 2.3.4 is the same
as an upgrade to 3.0 or 3.1 from SQL/MX Release 2.3.4.
• Metadata upgrade is optional if no new database features are used for the existing schemas.
• The format of the CPU lists stored in the ODBC/MX metadata, in SQL/MX Release 2.3.x is
different from the format of the CPU lists stored in SQL/MX Release 3.2. The SQL/MX Release
2.3.x CPU list format is not recognized in SQL/MX Release 3.2. 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 CPU list format in
the ENVIRONMENTVALUES MXCS metadata table. The fixmxcsmd option also supports
the conversion of the SQL/MX Release 3.2 CPU list format to the SQL/MX Release 2.3.x CPU
list format in the ENVIRONMENTVALUES MXCS metadata table.
Upgrading does not affect the standard RVU installation procedure.
Fallback Considerations
Fallback from the next RVU that includes these features to the previous RVU does not require
customer changes to applications or system management scripts or procedures, if the customer is
not using any new limits or features.
All metadata must be downgraded while the system is running SQL/MX Release 3.2, to a version
that is supported by the target release for the fallback.
SQL/MX Release 3.2 15