RE: Problem with native driver

Yes, we will use Connections pool. This should resolve our problem,
since each client will use a different connection. The connection pool
is synchronized and we can use a limited number of connections.

I'll tell you the results

Gilles

-----Original Message-----
From: Luther Ananda Miller [mailto:luther.miller@HYPERE.COM]
Sent: lundi, 7. février 2000 19:06
To: L-JAVA400@midrange.com
Subject: Re: Problem with native driver

Can't open two results from the same stored procedure from the same database
connection:
Yep- this is a terrible limitation.

Let's say you have a customer on the phone and you want to open two
telephone bill detail screens at the same time (for two different months) ..
can't do it if the details come back from a stored procedure. Hey, isn't
that why we use GUIs? We opened a PMR on it ages ago and for the response
that it was a feature of the system and if we wanted it change we would have
to submit a request for enhancement.

If you need to do it, then you need to have either multiple versions of the
same SP which are really identical, or multiple connections from the same
app, or use SELECT statement directly. Maybe it would be possible to use
dynamic SQL in the stored procedure and random generate cursor names with
each call, but I haven't tried. Wish this was on the top list of AS/400
database things-to-do...

But I think this should only be a problem if you do it from the same
database connection?

Luther
  ----- Original Message -----
  From: cujo@us.ibm.com
  To: DUCRET Gilles (GVA)
  Cc: 'JAVA400-L@midrange.com' ; DES ROSIERS Daniel (GVA) ;
ewarne@us.ibm.com ; MAZY Herv (GVA)
  Sent: Monday, 7 February 2000 15:46
  Subject: Re: Problem with native driver

  I believe your problem is that stored procedures are not a multi-threaded
  resource.  (I don't really know a better way to phrase that, but I am sure
  there is one).

  You should be able to create a similar problem in a single stand alone
  program by doing this:

  1) get a conection
  2) get 2 statements
  3) execute the strored procedure with the first statement (keep the result
  set open)
  4) execute the stored procedure with the second statement
       ***I would think you are going to get an error about the cursor being
  already open at this point

+---
| This is the JAVA/400 Mailing List!
| To submit a new message, send your mail to JAVA400-L@midrange.com.
| To subscribe to this list send email to JAVA400-L-SUB@midrange.com.
| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: joe@zappie.net
+---