Implementing Siebel eBusiness Applications on DB2 UDB for z/OS and OS/390 > Maintenance Considerations for zSeries > About Siebel Dynamic SQL >

Enabling DB2 CLI Tracing

DB2 Call Level Interface (CLI) tracing can be enabled by adding the following lines to the db2cli.ini file.

To enable DB2 CLI tracing

1. Enter a section into the DB2CLI.INI file called [COMMON].
2. Add the following entries to your DB2CLI.INI file.

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

One trace file will be created for each thread in the path specified. The path must already exist. On UNIX systems, the DB2 process owner must have the appropriate permissions to be able to write into the directory specified in the TracePathName.

The resulting files will be called pid.tid i.e. 382.0 or -23456.0. Only the trace files created at the time of problem recreation should be reviewed.

This section can be added into the db2cli.ini file for both Windows and UNIX clients. Each DB2 process will generate its own trace file. The events in the DB2 CLI trace are specific to DB2 clients.