Use server-side tools to help diagnose ODBC problems.
The following tables contain ODBC diagnostic and performance tools the server side:
| Communications trace | The communications trace facility will trace and format any communications
type that has a line description (token ring and Ethernet). This is a tool for isolating many problems. It also is a useful aid for diagnosing where a performance delay is occurring. Use the timestamp and eye-catcher fields to measure how long it takes to process a request. |
| Job traces | The job trace can help isolate most host problems and many performance
issues. A service job must first be started on the job to be traced. Locate
the fully qualified job name of the ODBC job. From any 5250 emulation session,
start a service job on this QZDASOINIT job by using the STRSRVJOB command.
Then choose one of two traces, depending on the information needed:
The STRDBG command runs against an active service job. This command logs the decisions made by the query Optimizer to the job log of the debug session. For example, it records estimated query times, access paths used, and cursor errors. An easy way to enable STRDBG is to configure the ODBC DSN you are using through ODBC Adminstrator by selecting the Enable the Start Debug (STRDBG) command option on the Diagnostic tab. Alternatively, you can run the following command: STRDBG UPDPROD(*YES) The ODBC job log can record all errors that occur on the iSeries™ server. When the job is in debug mode, the job log also will contain performance-related information. |
| Performance tools | Performance toolkit provides reports and utilities that can be used
to create an in-depth analysis of your application performance. The toolkit
provides information about CPU utilization, disk arm utilization, memory paging
and much more. Although the base operating system includes the ability to
collect performance data, you will need the separately licensed program Performance
Tools/400 to analyze the results. You can also use the tools Database Monitor and Visual Explain. Refer to the iSeries Navigator Online help for more information. |
| QZDASOINIT job log | To receive optimal support, generate, locate and retrieve the QZDASOINIT
job log. The job log may contain messages that can help you to determine and
resolve errors that are returned through ODBC. An easy way to access the job log is to configure the ODBC DSN you are using through ODBC Adminstrator by selecting the Print job log at disconnect option on the Diagnostic tab. To find the job log, open a PC5250 emulation session and run the WRKSPLF command. Specify the iSeries user profile that was used on the ODBC connection as the user parameter for the WRKSPLF command. |
| QAQQINI (Query options file) | You can set the library for Query options file, by configuring the ODBC DSN you are using through ODBC Adminstrator and selecting the Diagnostic tab. Enter the name of the library you want to use in the Query options file library box. |