MX Release 3.2 (H06.25+, J06.14+)

For more information about data sources, see the HP NonStop SQL/MX Connectivity Service

Manual for SQL/MX Release 3.x .

Client data source configuration

The client data sources are configured on the Linux workstation. When the driver uses the SQL/MX

driver manager, the client data sources are configured in MXODSN file. When the driver uses

unixODBC driver manager, the client data sources are configured in odbc.iniand odbcinst.ini

files.

The driver accesses the configuration file when it sends a connect request to MXCS. The driver

parses the configuration file and fetches the required data source configuration details. If the data

source is not configured on server, the application gets connected to the default data source,

TDM_Default_DataSource.

Server data source configuration

The server data sources reside on a NonStop server. For details about configuring and managing

server data sources, see the HP NonStop SQL/MX Connectivity Service Manual for SQL/MX

Release 3.x .

Default data source

TDM_Default_DataSource is the pre-configured default server data source. You can stop and

start TDM_Default_DataSource with NSM/web or SQL/MX Administrative Command Library

(MACL, mode mxcs invoked from mxci) or SQL/MX Remote Conversational Interface (RMXCI) or

SQL/MX Database Manager (available from SQL/MX Release 3.2 onwards), but you cannot

delete it.

MXCS establishes a connection with TDM_Default_DataSource when there is a mismatch in

the client and server data source names.

For more information about MACL, see the SQL/MX Connectivity Service Administrative Command

Reference .

Connections

To connect to a data source, the application sends a connection request with the client data source

name. MXCS matches the client data source name with server data source name (data source

names are case sensitive). MXCS establishes the connection when the client data source name

matches the server data source name. If the client data source name matches server data source

name, but the server data source is not started, MXCS rejects the connection request. If the server

data source does not exist, MXCS routes the connection to the default data source. If the default

data source is not started, MXCS rejects the connection.

For more information about how MXCS establishes connections, see the HP NonStop SQL/MX

Connectivity Service Manual for SQL/MX Release 3.x .

Tracing

The driver supports tracing. The trace information is captured in a log file. You can enable or

disable tracing and specify the trace file name in MXODSN file.

When using the unixODBC driver manager, you can enable the driver tracing by setting the

following environment variables:

• HPODBC_TRACE_LEVEL. For trace values, see “MXODSN file format” (page 17)

• HPODBC_TRACEFILE_NAME to set the trace file name. The PID and current time are appended

to the this name to form the final trace file name.

• HPODBC_TRACEFILE_SIZE to set the maximum trace file size. The default file size in 1 GB.

12 Overview