Java™ environment
guidelines and recommendations for pureQuery client optimization include
considerations for connection type, classpath settings, and DB2® for z/OS® data sources. In addition tools are available
for verifying configuration and property resolution.
- Connection type
- The Java application that
is enabled for pureQuery client optimization can connect to the database
with a Type-2 or a Type-4 connection. pureQuery Runtime works with
both connection types.
- CLASSPATH settings
- For an application, the environment variable CLASSPATH must contain
both the database driver JAR file and the pureQuery Runtime JAR file
pdq.jar. The pureQuery pdqmgmt.jar file and any other required driver
file and must also be present in the CLASSPATH. For example, when
you use the IBM® Data Server
Driver for JDBC and SQLJ, the environment variable CLASSPATH must
contain the database driver JAR file db2jcc.jar, the license JAR file
db2jcc_license_cisuz.jar, and the two pureQuery Runtime JAR files.
- z/OS data sources
- The JAR files are available on a z/OS system
when the IBM Data Server Driver
for JDBC and SQLJ and the pureQuery Runtime products are installed.
After
the installation of the driver and pureQuery Runtime on the z/OS system, the IBM Data Server Driver for JDBC and SQLJ JAR
files are available in the /usr/lpp/db2910/classes directory for the DB2 Version 9 system and the pureQuery
JAR files are available in the /usr/lpp/pqrnn/lib/IBM
directory. The nn is the release version of pureQuery
Runtime.
A database administrator or a user who has BIND privileges
and has UNIX® (USS)
on z/OS configured with the
required JAR files in the CLASSPATH can use pureQuery client optimization
with an application and make it execute SQL statements statically.
- Tools for verifying configuration and pureQuery property evaluation
- After installing and configuring pureQuery and configuring the
properties for a specific application or data source deployment, you
can use pureQuery Runtime to examine and verify the configuration
and property resolution. If pureQuery Runtime properties are specified
in more than one way for a specific application, a defined concatenation
and override sequence resolves the property settings. You can verify
the property settings in the environment in one of two ways:
- DataVersion utility
- Use this tool for standalone applications that run from a command
line. For example, you can use the DataVersion utility with the-configuration option
to get a report of pureQuery and JDBC driver levels and a complete
description of the pureQuery property resolution. This utility must
be run in the same environment that your application runs in to give
an accurate reporting of the property resolution. Using the DavaVersion
utility can be difficult in an application server environment. The
DataVersion utility can be invoked using methods in a Java program to retrieve the same driver and
property information. You must write and deploy an application into
the application server to gather and report the information.
- pureQuery logging capability
- You can use the pureQuery logging capability. Set the value of
pdq.traceLevel to CONFIG to see the information
about configuration and property evaluation. The output will describe
where pureQuery found properties specified and what the final resolution
of the concatenation and override processing was. If pureQuery Runtime
is not responding to your expected settings, or the log shows a different
configuration and property evaluation than expected, review this information
to understand how pureQuery resolves properties from various sources: Scope of pureQuery Runtime properties in a WebSphere Application Server environment.