Re: Problems Caching and reusing JDBC CallableStatement objects

Hai folks,
                     All of you talking about CallableStatements that 
tempted me to work on that. I normally uses PreparedStatements in my 
application, but when i started learning the Stored Procedures, i am very 
much wondered about the features of CallableStatements.
                     I have few problems, i want to know where to place the 
stored procedure, whether it has to be placed in the java pgm or should be 
placed in an AS/400 library..??. If some one give me the code snippet i will 
be thankful..There are any web sites available for this purpose..??

Thanks in Advance.

Regards,
Vijay.


>From: "Al Heitkamp" <Al.Heitkamp@hbfuller.com>
>Reply-To: JAVA400-L@midrange.com
>To: Java400-L@midrange.com
>Subject: Re: Problems Caching and reusing JDBC CallableStatement       objects
>Date: Mon, 24 Jul 2000 13:54:06 -0500
>
>Applying PTF SF63152 corrected the problem for us.  We are now able to 
>cache the  CallableStatements and reuse them.
>
>Thanks Richard!
>
>
>Alan A. Heitkamp
>H.B. Fuller Company
>(651) 236-4072
>Al.Heitkamp@hbfuller.com
>
> >>> <cujo@us.ibm.com> 07/17 9:56 AM >>>
>The latest JDBC PTF is SF63152.  It superceeds all others, so it would be
>what you want if you would like to be totally up to date.
>
>Try to build as simple of a recreation as you can and send it to me.  I
>will try to figure out what is going on.
>
>
>Regards,
>
>Richard D. Dettinger
>AS/400 Java Data Access Team
>
>"TRUE! nervous, very, very dreadfully nervous I had been and am; but why
>WILL you say that I am mad?
>The disease had sharpened my senses, not destroyed, not dulled them. "
>
>- Edgar Allan Poe
>"The Tell-Tale Heart"
>
>
>
>
>"Al Heitkamp" <Al.Heitkamp@hbfuller.com> on 07/17/2000 09:07:46 AM
>
>Please respond to JAVA400-L@midrange.com
>
>To:   JAVA400-L@midrange.com
>cc:
>Subject:  Re: Problems Caching and reusing JDBC CallableStatement
>       objects
>
>
>
>
>My AS/400 administrator informed me that we are current on PTFs.
>
>      Product ID/PTF ID  . . . . . . . . . . :   5769999  TL00147
>
>Are there any particular PTFs that I should ensure have been applied?
>
>Thanks,
>
>Al Heitkamp
>H.B. Fuller Company
>Arden Hills, MN
>
> >>> <cujo@us.ibm.com> 07/14 11:01 AM >>>
>Hmm... I think that should all work, but we have run into a couple issues
>recently with our parameter support.  Please ensure that you are pretty up
>to date on your v4r4 PTFs, and try again after getting the latest if you
>are not.
>
>If the problem persists, please try to find the simplest example that you
>can recreate the problem in and e-mail it to me directly.  I will figure
>out what is going on and get back to you and/or the group as appropriate.
>Thanks.
>
>Regards,
>
>Richard D. Dettinger
>AS/400 Java Data Access Team
>
>"TRUE! nervous, very, very dreadfully nervous I had been and am; but why
>WILL you say that I am mad?
>The disease had sharpened my senses, not destroyed, not dulled them. "
>
>- Edgar Allan Poe
>"The Tell-Tale Heart"
>
>
>
>
>"Al Heitkamp" <Al.Heitkamp@hbfuller.com> on 07/14/2000 09:40:48 AM
>
>Please respond to JAVA400-L@midrange.com
>
>To:   JAVA400-L@midrange.com
>cc:
>Subject:  Problems Caching and reusing JDBC CallableStatement objects
>
>
>
>
>I have written an application that runs on the AS/400 and calls stored
>procedures using JDBC driver com.ibm.db2.jdbc.app.DB2Driver. My first
>release of the application created a new CallableStatement object each time
>I called a stored procedure. This has been working fine for some time now.
>
>In an attempt to improve performance, I modified the application to cache
>the CallableStatement objects for each different stored procedure call,
>then reusing the CallableStatement object for subsequent stored procedure
>calls.  I am now getting the error *Conversion error on input host variable
>or parameter *N.* I returned to creating the new CallableStatement for
>every stored procedure call and the application works fine again. Caching
>the CallableStatements works fine against an Oracle database and improved
>performance by almost 10 percent.
>
>Has anyone seen this problem before?  We are running V4R4 and JDK 1.1.7.
>
>Thanks,
>
>Al Heitkamp
>H.B. Fuller Company
>Arden Hills, MN
>
>
>
>+---
>| 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
>+---
>
>
>
>+---
>| 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
>+---
>
>+---
>| 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
>+---
>
>
>
>+---
>| 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
>+---

________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com

+---
| 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
+---