pureQuery client optimization with CLI applications provides
mechanisms for record logging and file tracing with configurable severity
levels.
Before you begin
In order to use the pureQuery features, you must enable pureQuery
Runtime for your IBM® Data Server
CLI Driver version 9.7 Fix pack 3 or later, with the IBM Optim pureQuery Runtime 2.1 or later.
About this task
pureQuery client optimization provides logging and tracing
capabilities with configurable severity. Logging and tracing might
provide the necessary information at each level to support problem
determination at run time. The task explains how to set the runtime
properties of the pureQuery Runtime logging and tracing capabilities
You
can set the following two keywords as an application connection property
or in the
db2cli.ini or
dsdriver.cfg configuration
file:
- traceFile
- Specifies the file where the log information written. You can
use an absolute path or a relative path to the directory in which
the CLI application runs. If the file exists, new log messages are
appended to the existing content of the file.
- traceLevel
- Specifies the level of detail to write to the log file. In order
from the least to the most detail, the levels are:
- OFF
- SEVERE
- WARNING
- INFO
- CONFIG
- FINE
- FINER
- FINEST
- ALL
The default level is OFF.
The keywords can be specified as an application
connection property, in
db2cli.ini file, or in
a
dsdriver.cfg file. If a keyword is specified
in multiple locations, the order of precedence from highest to lowest
is as follows:
- Application connection property
- db2cli.ini file
- dsdriver.cfg file
Example
The following lines set the traceFile to /user/CLIOPTtraces.log
and the traceLevel to INFO in the db2cli.ini file:
traceFile=/user/CLIOPTtraces.log
traceLevel=INFO
Alternatively, if you use a db2dsdriver.cfg
file, you set the keywords as attributes in parameter elements:
<parameter name="traceFile" value="/user/CLIOPTtraces.log" />
<parameter name="traceLevel" value="INFO" />