MX Release 3.2.1 (H06.26+, J06.15+)

driver forwards the request to MXCS, which authenticates the connection parameters. After successful

authentication, MXCS assigns an ODBC server to the application.

• If the data source is configured, but not started, then MXCS returns an error.

• If the data source is not configured on the server, then MXCS forwards the connect request to

the default data source, TDM_Default_DataSource.

After the connection is established, MXCS forwards the application requests to the SQL/MX

database engine, and sends the responses from the database engine to the driver. The

communication between the driver and MXCS is over TCP/IP sockets in the client-server parlance.

The IP address and the port number for the communication is configured in the MXODSN file.

NOTE: The connection pooling feature is not verified and it may work with driver manager

connection pooling. HP does not support or guarantee fixes for issues with this feature.

Client components

The following client components must be installed on the Linux workstation:

• Linux ODBC application, which is a user-written application or third-party product that uses

the ODBC APIs.

• 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 make multiple ODBC API calls internally

• Linux ODBC/MX client driver, which is an interface for Linux ODBC applications to access

an SQL/MX database.

Server components

The server components are installed on the NonStop system and comprises of:

• MXCS. For details, see the HP NonStop SQL/MX Connectivity Service Manual for SQL/MX

Release 3.x.

• SQL/MX database ( Release 3.x ). For details, see the SQL/MX 3.x Reference Manual.

Driver managers

The applications can use either the unixODBC open source driver manager version 2.2.14 or

later, except 2.3.0 or the SQL/MX driver manager. The applications can directly link with the

unixODBC library while compiling 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.

Data sources

Data sources are logical groupings of connections to the SQL/MX database. There are two types

of data sources.

• Client data source, commonly known as Data Source Name (DSN). The DSN is configured

on the Linux workstation.

• Server data source, which you must define and start on the NonStop system.

The driver uses the client data source configuration to route the ODBC API requests to MXCS.

Client components 11