JT400 / JTOpen Statement Pooling -- 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: JT400 / JTOpen Statement Pooling
From: "Etienne Richards" <etienne@xxxxxxxxxxxxx>
Date: Tue, 18 Mar 2003 21:30:02 -0500
Importance: Normal
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 iSeries / AS400<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>

All (and Joe Pluta),

Today I had a nice long conference call with IBM regarding JDBC and
Connection Pooling, Prepared Statement Pooling and Extended Dynamic
settings.

I am troubled...

1. Does the latest JT400 jdbc driver do prepared statement pooling?
        1.1. If it does, how do I enable it?
        1.2. If it does not, when will it?

2. Is it worth using the extended dynamic settings that are available in
JT400 if the client is not running on an AS/400?

3. How does caching of Access Paths (Extended Dynamic) and Prepared
Statement pooling relate to each other. How are the caching of Access Paths
and ODP's different (as viewed from a jdbc client)?

4. Would you recommend using the JT400 connection pool for applications that
are not running in WebSphere?

Any comments or answers would be appreciated.

Thanks,
Etienne

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: JT400 / JTOpen Statement Pooling , Joe Pluta

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.