RE: JT400 / JTOpen Statement Pooling

Etienne, why are you troubled?  IBM owns JT400 (and JTOpen), so I would have
thought you would have asked them these questions.

Let me try to address a few things, though:

1. What do you think prepared statement pooling is?  Remember, JDBC 3.0
doesn't say anything about the implementation of PSP, simply that there is
an interface for it.  Now, do you expect PSP to work across sessions, across
connections, or only within a single connection?

2. Which settings?

3. I don't know that they relate at all.

4. I recommend connection pooling for any application that has an unknown
but potentially very large number of connections.  This is typically the
case in an Internet application.  For a smaller number of users, I still
prefer persistent connections held at the session level.


> -----Original Message-----
> From: java400-l-bounces@xxxxxxxxxxxx
> [mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of Etienne Richards
> Sent: Tuesday, March 18, 2003 8:30 PM
> To: java400-l@xxxxxxxxxxxx
> Subject: JT400 / JTOpen Statement Pooling
>
>
> 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