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

3 Configuring data sources

This chapter describes the SQL/MX driver manager configuration. For details about unixODBC

driver manager configuration, see the unixODBC website: http://www.unixodbc.org.

This chapter describes the following:

• “Configuring client data sources” (page 17)

• “MXODSN file format” (page 17)

• “Managing data sources” (page 20)

• “Tracing” (page 20)

• “Setting the MXODSN file path in DSN_PATH” (page 20)

Configuring client data sources

The MXODSN file, which is a text file, is a repository of all client data sources.

You can place the MXODSN file in any one of the following locations:

• Location specified in DSN_PATH environment variable

• Linux ODBC application directory

• Default system location, /etc/hpodbc

To configure a client data source, edit the MXODSN file. Change this file so that the attributes are

set to the correct values for your system (for example, names of data sources and attributes

describing them).

The DSN in the MSODSN file must exactly match the server data source name (data source names

are case sensitive). If the data source names do not match, the application gets a warning that

connection is established with default data source, TDM_Default_DataSource.

The driver uses default values for CATALOG and SCHEMA attributes if you have not defined them

in the MXODSN file.

The search order for the MXODSN file is:

1. Location specified in DSN_PATH environment variable

2. Linux ODBC application directory

3. Default system location, /etc/hpodbc

MXODSN file format

Table 2 (page 17) describes the MXODSN file sections and attributes.

Table 2 MXODSN file format and attributes

DescriptionAttributesFile section

TraceStart can have two values, 0 or

1. If set to 0, tracing is off. If set to 1,

tracing is on. By default, tracing is off.

TraceStart

TraceFlags

TraceFile

[ODBC]

TraceFlags indicates the trace level. It

can have the following values:

• ERROR to trace failed SQL calls and

communication problems.

• WARNING to trace the warnings.

• CONFIG to trace configuration calls.

Configuring client data sources 17