Easysoft ODBC-DB2 Driver User's Guide - Technical Reference

Technical Reference for the Easysoft ODBC-DB2 Driver

This section contains extra information relating to the deployment of the Easysoft ODBC-DB2 Driver.

Appendix Guide

ODBC Conformance

The Easysoft ODBC-DB2 Driver complies with the ODBC 3.52 specification.

The Easysoft ODBC-DB2 Driver is Level 2 compliant.

ODBC API Support

All ODBC 3.52 calls are supported.

Tracing

The ODBC calls an application makes can be traced:

Within the driver manager by an application

An application can turn tracing on in the Driver Manager by using the ODBC API SQLSetConnectAttr (...,SQL_ATTR_TRACE,...).

The trace file name may also be specified with the SQLSetConnectAttr attribute SQL_ATTR_TRACEFILE.

From within the driver manager on Windows

Click on Tracing, ensure the specified filename is valid and click Start Tracing Now.


64-bit Windows

There is both a 64-bit and 32-bit version of the ODBC Data Source Administrator. The 64-bit version enables you to trace the ODBC API calls that are made by a 64-bit application. The 32-bit version enables you to trace the ODBC API calls that are made by a 32-bit application.

The 64-bit version is located in Control Panel (see the previous step). To run the 32-bit version on Windows 7 and earlier, in the Windows Run dialog box, type:

%windir%\syswow64\odbcad32.exe

On Windows 8, both the 32-bit and 64-bit ODBC Administrator are located in Control Panel under Administrative tools: ODBC Data Sources (32-bit) and ODBC Data Sources (64-bit).

If you are not sure which version to use, and do not get a log file after completing the steps in this article, try enabling tracing in the other version of ODBC Data Source Administrator.


From within the driver manager on Unix

For the unixODBC Driver Manager, add two attributes to the [ODBC] section (create one if none exists) in odbcinst.ini.

Trace = Yes

TraceFile = logfile

For example:

[ODBC]

Trace = Yes

TraceFile = /tmp/unixodbc.log

Ensure that the user who is running the application to be traced has write permission to the log file (and to the directory containing it), or no tracing information will be produced.

From within the Easysoft ODBC-DB2 Driver

Driver manager trace files show all the ODBC calls applications make, their arguments and return values. Easysoft ODBC-DB2 Driver driver tracing is specific to the Easysoft driver and is of most use when making a support call.

From within the Easysoft ODBC-DB2 Driver on Unix

To enable Easysoft ODBC-DB2 Driver logging, add a LOGFILE and a LOGGING attribute to the relevant DSN section of the odbc.ini file.

For example:

[DB2_SAMPLE]

.

.

.

LOGFILE = /tmp/db2-driver.log

LOGGING = Yes

The LOGFILE value is the path and file name of the log file. The value shown in the example specifies a log file named /tmp/db2.log. The LOGGING value specifies the actions to log. The value shown in the example specifies that all actions should be logged.

Ensure that the user who is running the application to be traced has write permission to the log file (and to the directory containing it).

By default, the Easysoft ODBC-DB2 Driver appends log information to the file specified by LOGFILE. If you want the driver to generate a new log file for each ODBC session, enable logging on a per process basis. To do this, change the LOGGING entry to:

LOGGING = Process

When you set LOGGING to Process, the Easysoft ODBC-DB2 Driver creates separate log files that only contain trace output related to a particular driver process. The log file name contains the ID of the driver process that the log output is associated with. For example, /tmp/db2-driver.log.0000266F.B7D766C0.

From within the Easysoft ODBC-DB2 Driver on Windows

To enable logging:

1.  Open the relevant Easysoft ODBC-DB2 Driver data source in ODBC Data Source Administrator.

2.  Click Driver Logging.

3.  Type the file name and path of the file you want the driver to write log information to in the space provided.