skip to main content
Configuring Hybrid Data Pipeline Driver for ODBC : Application considerations : Verifying the driver version number : Driver Manager version string (UNIX/Linux)
  

Try Now
Driver Manager version string (UNIX/Linux)
Note: The driver uses the same Driver Manager as the Progress DataDirect Connect for ODBC drivers. For this reason, the Driver Manager version does not correspond to the version of the Hybrid Data Pipeline for ODBC driver.
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.
BBBB
is the build number of the product's utl component.
For example:
07.10.0001  (U0001)
       |__|   |___|
      Driver   Utl
On UNIX and Linux, you can check the version string by using the test loading tool shipped with the product. This tool, ivtestlib, 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 Driver Manager on Solaris:
ivtestlib libodbc.so
returns:
07.10.0001 (U0001)
For example, for the 64-bit Driver Manager on Solaris:
ddtestlib libodbc.so
returns:
07.10.0001 (U0001)
For example, for the 32-bit ICU component on Solaris:
ivtestlib libivicu27.so
returns:
07.10.0001
Note: On AIX, Linux, and Solaris, the full path to the product does not have to be specified for the test loading tool. The HP-UX version of the tool, however, requires the full path.