Re: AS400/DB2 - caching specific query -- JAVA400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: AS400/DB2 - caching specific query
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 02 Feb 2012 08:59:14 -0600
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the IBM i <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

On 2/2/2012 1:39 AM, Tomer Sason wrote:

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?

If you set the trace level to SERVER_TRACE_DEBUG_SERVER_JOB, for the data source, you should get the debug information that you need.

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: AS400/DB2 - caching specific query , Tomer Sason

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.