The Driver Manager on UNIX and Linux has a version string of the format:
XX.YY.ZZZZ(UBBBB)
The component for the Unicode conversion tables (ICU) has a version string of the format:
XX.YY.ZZZZ
where:
XX is the major version of the product.
YY is the minor version of the product.
ZZZZ is the build number of the driver or ICU component.
AAAA is the build number of the driver's base component.
BBBB is the build number of the driver's utl component.
For example:
08.00.0001 (b0001, u0002)
|__| |___| |___|
Driver Base Utl
On Windows, you can check the version string using the properties window of the driver file. First, right-click the driver .dll file and select Properties. Then, on the Properties window, select the Details tab. The product version field lists the version string.
You can always check the version string of a driver on Windows by looking at the About tab of the driver’s Setup dialog.
On UNIX, Linux and macOS, you can check the version string by using the test loading tool shipped with the product. This tool, ivtestlib for 32-bit drivers and ddtestlib for 64-bit drivers, is launched using a command-line and is located in install_directory/bin.
The syntax for the tool is:
ivtestlib shared_object
or
ddtestlib shared_object
For example, for the 32-bit Wire Protocol driver on Linux:
ivtestlib ivora28.so
returns:
08.00.0001 (B0002, U0001)
For example, for the Driver Manager on Linux:
ivtestlib libodbc.so
returns:
08.00.0001 (U0001)
For example, for the 64-bit Driver Manager on Linux:
ddtestlib libodbc.so
returns:
08.00.0001 (U0001)
For example, for 32-bit ICU component on Linux:
ivtestlib libivicu28.so
08.00.0001
Note: Only the HP-UX version of the tool requires specifying the full path for the test loading tool. The full path does not need to be specified for other platforms.