There are various methods for initiating trace for ODBC activity,
depending on the operating system that you are using:
For Windows, use the Tracing tab
of the ODBC function:
To stop ODBC tracing, on the Tracing tab,
click Stop Tracing Now,
then OK.
For
Linux and
UNIX operating
systems, edit the
ODBC.ini file to initiate trace for
ODBC activity (if you are using the default
ODBC.ini file,
located at
/var/wmqi/odbc/.odbc.ini):
- Under the stanza entry [ODBC], change Trace=0 to Trace=1
- Optionally, modify the TraceFile file path value
to a preferred value. All trace records go to one file, which can be confusing
if you have multiple flows or execution groups.
For
z/OS,
edit the
BIPDSNAO file in the component dataset
to initiate application trace for ODBC activity:
- Under the stanza entry [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
if you have multiple flows or execution groups.
Trace information is output to the location that is specified
in the .odbc.ini file, or in the ODBC configuration on Windows. By default on non-Windows systems,
this is /var/wmqi/odbc/odbctrace.out.