Open System Services ODBC/MX Client Driver Manual for SQL/MX Release 3.2.1 (H06.26+, J06.15+)
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.
Configuring OSS ODBC/MX driver to use IPV6
The steps to configure OSS ODBC/MX driver to use IPV6 are:
1. Verify that the TCPIP DEFINE is set to use Ipv6, when the ODBC client is started.
2. Skip this step if you have set DEFINE to TCP6SAM process.
Use the following commands to delete the existing DEFINE and to create a new one:
• For deleting the existing DEFINE, use
delete define =TCPIP^PROCESS^NAME
• For adding a DEFINE with Ipv6, use
add define =TCPIP^PROCESS^NAME, class MAP, file “\KRYPTON.$ZSAM0”
where:
\KRYPTON is the machine name.
$ZSAM0 is the TCP6SAM process name.
For more information, see the TCP/IP Configuration and Management Manual.
3. Start the OSH/OSS process. If the process is started directly, the environmental variable
TCPIP_PROCESS_NAME must point to Ipv6 process.
4. Set the configuration variable Ipv6 to Enable in the ODBCDSN file.
Ipv6=Enable
NOTE: The variable, Ipv6 is case sensitive, where as Enable is not case sensitive.
Any error in the configuration process sets the driver to Ipv4, which is the default.
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
Configuring Data Sources 25










