MX 2.x)

ODBC/MX Client Overview

HP NonStop ODBC/MX Driver for Windows—527888-004

1-2

Client Data Sources

using NSM/web, but you cannot delete it. The TDM_Default_DataSource has these

functions:

•

ODBC clients can connect to TDM_Default_DataSource and access a NonStop

SQL database with no special configuration required.

•

If an ODBC client tries to connect to a data source in the NonStop system and the

client data source name and the NonStop system data source name do not match

(including the case), the association server connects the ODBC client to

TDM_Default_DataSource.

Client Data Sources

Client data sources reside on a client workstation. Each client data source is a logical

name that identifies the attribute values used to connect to the MXCS service and

defines some local behavior for the connection. Use the Microsoft ODBC Data Source

Administrator to add, configure, and remove ODBC/MX client data sources.

Connections

Connecting a Client to a Data Source

Figure 1-1 shows the flow of data among the ODBC/MX components.

The MXCS association server starts and manages the MXCS servers associated with

MXCS data sources in the NonStop system. When an ODBC client requests a

connection to a data source, the association server also associates the client with an

available MXCS SQL server. The following scenario describes how an ODBC client

application connects to an MXCS SQL server through the association server:

1. The ODBC client application sends a connection request to the MXCS service

using the client data source name. The client data source name specifies an IP

address and port number or NonStop server name that is defined when you start

the association server.

2. The association server grants the connection request and associates the ODBC

client application with an available MXCS SQL server for the data source. (If the

association server does not find the requested data source name, it assigns a

server associated with the default data source.)

3. The ODBC client application sends a connection request to the MXCS SQL server

that was assigned by the association server. If the user information is not valid, the

connection is rejected.

4. When the ODBC client application disconnects, the MXCS SQL server notifies the

association server that it is available for connections from other ODBC clients and

returns to the server data source pool.

Note. If an ODBC client tries to connect to a server data source that is stopped, MXCS

rejects the connection.