Open System Services ODBC/MX Client Driver for SQL/MX Release 3.2 (H06.25+, J06.14+)

For details on attributes and settings in the ODBCDSN file, see Table 4.2.1, Format of the
ODBCDSN file, and, Example ODBCDSN file.
2. Move the ODBCDSN file to the $SYSTEM.SYSTEM folder.
The OSS ODBC/MX driver first searches for the ODBCDSN file in the same OSS directory
as the executable file of the process. If the ODBCDSN file is not available, the driver searches
for it in $SYSTEM.SYSTEM.
You can also save the ODBCDSN in the OSS location where the executable program is to
be run. If you save the ODBCDSN file in the OSS location, it will take precedence over the
ODBCDSN available at the $SYSTEM.SYSTEM location.
ODBCDSN File Format
Table 2 -1 describes the format of the ODBCDSN file.
Contents and FormatFile Section
Trace information[ODBC]
DescriptionTrace Attribute
Trace off = 0TraceStart
Trace on =1
If TraceStart keyword is omitted,
TraceStart = 0
Name of the file that includes the
tracing information and it resides in the
TraceFile
OSS location where the program is
executed. Trace file name is specified
in the following format:
TraceFile = file_name
For example, if you specify the name
of the trace file as Tracefile =
trfetch, the system creates a file
name as
trfetch.6947088_1285815329.
This file is located in the OSS location
even if the ODBCDSN file is in the
$SYSTEM.SYSTEM location.
Bitmask indicating trace level. For
ODBC/MX 3.x:
TraceFlagsFile Section
If TraceFlags keyword is omitted,
TraceFlags = 0
TraceFlags can take the following
values:
• ERROR—Indicates some failed SQL
calls and communication problems.
• WARNING—Triggered by anything
that generates a diagnostic record.
• CONFIG—Provides details of
configuration calls.
• INFO—Provides details of what calls
are made and other important
markers.
• DEBUG (or number 6)—Shows the
detailed contents of many calls.
Configuring Data Sources 25