DB2 10.5 for Linux, UNIX, and Windows

TracePathName CLI/ODBC configuration keyword

Specifies the subdirectory to be used to store individual CLI/ODBC trace files.

db2cli.ini keyword syntax:: TracePathName = < fully qualified subdirectory name >
Default setting:: None
Only applicable when:: the Trace option is turned on.
Not applicable when:: the TraceFileName option is turned on.
Usage notes:

Each thread or process that uses the same DLL or shared library will have a separate CLI/ODBC trace file created in the specified directory. A concatenation of the application process ID and the thread sequence number is automatically used to name trace files.

No trace will occur, and no error message will be returned, if the subdirectory given is invalid or if it cannot be written to.

This option is only used when the Trace option is turned on. This will be done automatically when you set this option in the CLI/ODBC Configuration utility.

It will be ignored if the CLI/ODBC option TraceFileName is used.

CLI trace should only be used for debugging purposes. It will slow down the execution of the CLI/ODBC driver, and the trace information can grow quite large if it is left on for extended periods of time.

If both TraceFileName and TracePathName are specified, the TraceFileName keyword takes precedence and TracePathName will be ignored.

(This option is contained in the Common section of the initialization file and therefore applies to all connections to DB2®.)