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

The SQL ODBC Applications interact with the OSS ODBC/MX Client Driver to communicate to

the SQL/MX database. The ODBC server establishes a connection between the OSS ODBC/MX

Client Driver and the SQL/MX database. The ODBC server interacts with the SQL/MX database,

forwards the client requests to the database engine, and sends the responses to the OSS ODBC/MX

Client Driver.

The ODBC/MX APIs are directly exposed to the ODBC applications. The OSS ODBC/MX Client

Driver exposes a set of APIs, which calls multiple ODBC APIs internally. These APIs depict a thin

layer of driver manager to the OSS ODBC/MX Client Driver. Minimal OSS ODBC/MX Driver

Manager functionalities are included within the Driver code.

When the ODBC client application runs the SQLConnect() function to request for a data source,

a connection is established between the OSS ODBC/MX Client Driver and the Association Server

(MXOAS). The Association Server checks the status and the configuration details of the requested

data source in the ODBCDSN file.

Meanwhile, the OSS ODBC/MX Client Driver waits for the reply from the Association Server.

The following scenarios describe what steps the Association Server perform depending on

configuration and status of the data source.

If the data source is configured and is in a running state, the Association Server replies to the OSS

ODBC/MX Client Driver after authenticating the client driver credentials. The OSS ODBC/MX

Client Driver then connects to the MXOSRVR after receiving a success reply from the Association

Server. User authentication is performed in the MXOSRVR as required for the SQL Executor. After

OSS ODBC/MX Client Driver Architecture 15