ODBC trace for WebSphere Message Broker

Depending on the platform you are using, use the procedure below to initiate trace for ODBC activity.

Windows

• Use the Tracing tab of the ODBC function, as follows:
  • Click Start > Settings > Control Panel > Administrative Tools.
  • Double-click Data Sources.
  • Select the Tracing tab. The Log File Path displays the default path and file name (/sql.log) trace information is written to.
  • Click the Start Tracing Now button.
  • Click OK.
  • To stop ODBC tracing, go to the same panel and click the Stop Tracing Now button, then click OK.

UNIX

• Edit the odbc.ini (V6.0 and V7) or odbc64.ini (V6.1) or odbcinst.ini (V8.0) file to initiate trace for ODBC activity (look for environment variable ODBCINI for V6.x and V7 and ODBSYSINI for V8):
  • Under the stanza entry [ODBC] change Trace=0 to Trace=1
  • Optionally, modify the TraceFile file path value to a preferred value.
  • Restart the broker.
    All trace records go to one file, which can be confusing with multiple flows or execution groups.

z/OS

• Edit /component_HFS/dsnaoini (V6.x and V7) and BIPDSNAO file (for V8) to initiate application trace for ODBC activity:
  • Under the stanza [COMMON] change APPLTRACE=0 to APPLTRACE=1
  • Optionally, modify the APPLTRACEFILENAME file path to a preferred value. All trace records go to one file, which can be confusing with multiple flows or execution groups.
    

Trace information is output to the file install_dir, which should help you to diagnose the problem.

After a PMR is open, submit the ODBC trace file to IBM Support for problem determination.

For a listing of all technotes, downloads, and educational materials specific to ODBC connections, refer to Knowledge Collection: Database Connectivity / ODBC / JDBC for WebSphere Message Broker or search the WebSphere Message Broker support site.