Use client-side tools to help diagnose ODBC problems.
The following table contains ODBC client-side diagnostic and performance tools:
| ODBC Trace (SQL.LOG) | Microsoft's ODBC Administrator provides its own trace utility to trace
ODBC API calls from applications. See Collecting an ODBC Trace (SQL.LOG) for more information. |
| ODBC trace utilities | There are other ODBC trace utilities available that can be more robust than the ODBC Trace (SQL.LOG). These retail utilities can provide detailed entry and exit point tracing of ODBC API calls. Two tracing utilities are Trace Tools (Dr. DeeBee) and SST Trace Plus (Systems Software Technology). |
| CWBPING | To use CWBPING, type cwbping (your system name or IP address) at
a command prompt. For example: cwbping testsys1 or cwbping
127.127.127.1 CWBPING responds with a list of servers, and their status. Run CWBPING without any parameters for help with using CWBPING. For more information about CWBPING, see Checking the server status. |
| CWBCOTRC | To use CWBCOTRC, type CWBCOTRC ON at a command prompt while located in the \Program Files\IBM\Client Access directory. After turning on the trace, you can start your application. Typing CWBCOTRC OFF stops tracing. CWBCOTRC gathers information about data that is being transmitted to and from the server. Run CWBCOTRC without any parameters for help with using CWBCOTRC. |
| Detail trace | Detail trace gathers information traced out by the iSeries™ Access for Windows® components that are in use. ODBC information that can be found in this trace includes entry points into the driver, information about the prestart job, the package name in use, and special error conditions. For more information, see Gather a detail trace. |