Restricts the process IDs for which the CLI/ODBC trace
will be enabled.
- db2cli.ini keyword syntax:
- TracePIDList = <no value specified> | <comma-delimited list of process IDs>
- Default setting:
- All of the process IDs will be traced when the CLI/ODBC trace
is run.
- Usage notes:
-
Use this keyword for applications that create many processes.
Capturing the CLI/ODBC trace for such applications can generate many
trace files. By using this keyword you can collect the trace of specific
problematic processes of applications.
If no value is specified
for this keyword, all process IDs will be traced. Otherwise, specify
a comma-delimited list of process IDs which you want to be traced
when the CLI/ODBC trace runs.
The TraceRefreshInterval keyword
must be set to some value before initializing your application, otherwise,
the TracePIDList keyword will not take effect.
(This option
is contained in the Common section of the initialization file and
therefore applies to all connections to DB2® databases.)
To use the TracePIDList keyword:
- Ensure the Trace CLI/ODBC keyword is set to zero or is not specified
in the db2cli.ini file.
- Add the TraceRefreshInterval CLI/ODBC keyword to the Common section
of the db2cli.ini file as follows:
[COMMON]
TraceRefreshInterval=<some positive integer>
- Start your application.
- Using an operating system command such as ps (on a UNIX and Linux-based operating systems), determine the
process IDs of the processes that you want to collect the CLI/ODBC
trace for.
- Turn CLI/ODBC tracing on and add the process IDs identified to
the Common section of the db2cli.ini file by including the following
keywords:
[COMMON]
Trace=1
TracePathName=<fully-qualified subdirectory name>
TracePIDList=<comma-delimited list of process IDs>
CLI/ODBC traces containing information of the process IDs specified
will be located in the directory specified by the TracePathName keyword..
You might also see extra empty files that can be ignored.