J06.09 Release Version Update Compendium

• The OSS ODBC/MX Client Driver is thread-aware and thread-safe, which means that it can
be used with multi-threaded C/C++ programs that use the T1248 standard POSIX thread
library.
• The statistics and trace information is now captured in the Event Management Service (EMS)
even when it is enabled for the existing client connections.
Migration Considerations
To use the SQL/MX 2.3.4 features, a new version of the JDBC T2 driver, T1275 H50 AAR, must
be installed on the systems running J06.09 or later J-series RVUs.
Fallback Considerations
If you have created tables on a SQL/MX Version R2.3.4 with new referential actions (CASCADE,
SET NULL, and SET DEFAULT) and you fallback to a version earlier than SQL/MX version 2.3.4,
tables that have new referential actions (CASCADE, SET NULL, and SET DEFAULT) exhibit NO
ACTION behavior for Data Manipulation Language (DML) operations. However, the metadata
continues to have new referential actions. Subsequently, if SQL/MX is again upgraded to version
2.3.4, the DML operations are executed as per the new referential actions. To avoid this change
in behavior, either drop the referential integrity constraints before falling back to an earlier
version or use the DOWNGRADE CASCADE option with the FIXUP operation. The
DOWNGRADE CASCADE option converts the new referential actions to NO ACTION.
JDBC T2 Driver and SQL/MX 2.3.4 Compatibility Requirements
The J06.09 RVU introduces several SQL/MX 2.3.4 enhancements, which are described in “SQL/MX
2.3.4 Enhancements” (page 15). These features require a new version of the JDBC T2 driver
(T1275H50 AAR) be installed on systems running J06.09 or later J-series RVUs.
16 Database and Transaction Processing Products