× 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: ProgramCall versus JDBC
  • From: "Luther Ananda Miller" <luther.miller@xxxxxxxxxx>
  • Date: Wed, 22 Mar 2000 08:32:43 +0100
  • Organization: HYPERe

I haven't used ProgramCall but based on what I read in previous posts on the
list I think you need to open another connection type to the AS/400 to run
ProgramCall. Some people depend on the program called creating data in QTEMP
which they want to read from the JDBC connection. Since they are two
different physical connections they could not do it that way- but calling
the program using JDBC would use the same connection and then they could
read the data from QTEMP. I imagine under the hood the call is different as
well- perhaps there is less overhead in the ProgramCall version since it
does not use the SQL modules on the AS/400 (QSQCALL??).

Luther

----- Original Message -----
From: Mark Sievers <MSievers@promega.com>
To: <JAVA400-L@midrange.com>
Sent: Tuesday, 21 March 2000 20:12
Subject: ProgramCall versus JDBC


> What is the difference between using the ProgramCall component to call a
> program or using JDBC to call a store procedure.  I know that you can
return
> one or many result sets if you use JDBC.  Are there a performance
> differences?
>
> Mark


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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.