Implementing Siebel Business Applications on DB2 UDB for z/OS > Maintenance Considerations for z/OS > Dynamic SQL in the Siebel Application >

Enabling DB2 CLI Tracing

You can enable DB2 Call Level Interface (CLI) tracing by adding the following lines to the db2cli.ini file (this procedure applies to Windows and UNIX).

To enable DB2 CLI tracing

1. Add a section to the db2cli.ini file labeled [COMMON].
2. Add the following entries to the [COMMON] section.

   [COMMON]
   Trace=1
   TracePathName=C:\TRACE
   TraceFlush=1
   TraceComm=1

For each thread, one trace file is created in the path specified in TracePathName (ensure you have already created the path). On UNIX systems, the DB2 process owner must have the appropriate permissions to write to the directory specified in TracePathName.

The resulting trace files are called pid.tid i.e. 382.0 or -23456.0. Only review the trace files created at the time of problem recreation.

Each DB2 process generates its own trace file. The events in the DB2 CLI trace are specific to DB2 clients.