HP Integrity NonStop H-Series - Manual (Page 12)

MXODSN file, and for the OSS driver in the ODBCDSN file. Use the Microsoft ODBC Data Source
Administrator to configure the parameters for the Windows driver.
Client components
The common client components are the ODBC applications, which are user-written or third-party
products that use the ODBC APIs, and the driver for the application platform. Install the following
client components for HP-UX, Linux, and Windows platforms:
HP-UX
•
unixODBC driver manager (only required for standalone driver,
libmxodbc_ia64_drvr.sl
), which is the open source driver manager implementation
that you can download from the unixODBC website http://www.unixODBC.org .
•
SQL/MX driver manager, which is the driver manager implementation from HP and includes
a set of APIs, which internally makes multiple ODBC API calls.
Linux 32
•
unixODBC driver manager (only required for standalone driver, libmxodbc_l_drvr.so),
which is the open source driver manager implementation that you can download from the
unixODBC website
http://www.unixODBC.org .
•
SQL/MX driver manager, which is the driver manager implementation from HP and includes
a set of APIs, which internally makes multiple ODBC API calls.
Linux 64
•
unixODBC driver manager (only required for standalone driver,
libmxodbc64_l_drvr.so
), which is the open source driver manager implementation
that you can download from the unixODBC website http://www.unixODBC.org .
•
SQL/MX driver manager, which is the driver manager implementation from HP and includes
a set of APIs, which internally makes multiple ODBC API calls.
Windows
•
Microsoft ODBC Driver Manager version 3.5.1 or later, which manages ODBC API
requests to ODBC drivers.
•
Microsoft ODBC Data Source Administrator.
Server components
The following server components are required on the NonStop system:
•
SQL/MX database release 3.2.1
•
MXCS
Driver managers
The HP-UX or Linux applications can use either the unixODBC driver manger versions 2.2.14, or
2.3.1 and later, or the SQL/MX driver manager. When compiling, the applications can directly
link with the unixODBC library or can use connectors to communicate with the driver manager.
The driver manager uses the information provided by the applications and routes the ODBC API
calls to the driver.
For more information about unixODBC driver manager, see the unixODBC website http://
www.unixODBC.org .
The Windows applications use the Microsoft ODBC Driver Manager version 3.5.1 or later.
12 Overview