RE: AS400/DB2 - caching specific query

Hi David,

We are using AS400JDBCConnectionPool to get the connection.
It is written in the documentation that "You must start tracing before connecting to the system ...".
Is there a way to specify the debug mode for a specific connection that created by the pool or for the entire pool?

Regards,
Tomer




-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Wednesday, February 01, 2012 7:15 PM
To: Java Programming on and around the IBM i
Subject: Re: AS400/DB2 - caching specific query

On 2/1/2012 8:59 AM, Tomer Sason wrote:

When I execute a query the first time, It's taking long time
(relatively speaking). The next executions time of the same query are
significantly shorter. If I do not use this specific query for a
while, the next time of execution gets longer again It seems that the
query was cached and after a while it was removed from the cache.

If you run the query in debug mode (there are properties on the jdbc connection you can set to enable debug), you can see the access path adviser messages ... if you create the recommended access paths, your queries will run faster always.

See http://urlq.us/jdbcprops or http://javadoc.midrange.com/jtopen/com/ibm/as400/access/doc-files/JDBCProperties.html for the properties.

david