Re: Retrieving integer parameter after JT400 ProgramCall?

Hi Thorbjørn,

Having it work with JDBC means that it will work with any language that
can talk to the database and not only Java.

I assume you really mean the SQL portion. The Java JDBC portion is not
going to work with another language without conversions, etc. as with any
other multi-language app.

Is there any other database connector which can be carried around like
jt400/jtopen or do they all require Client Access installed?

ODBC, although you need a language that understands ODBC - Java's ODBC
bridge has never been recommended for production quality applications.. As
an example of something that seems inefficient on the face of it, in my last
project, we had to get a table with AS/400 data to a SQL Server database.
SQL Server will actually do distributed queries with minor setup, so we
dumped the AS/400 ODBC driver in SQL Server.

In a case similar to Samuel Johnson's dancing dog, it's amazing that it
will do it, but it's dog (a pun - serendipity) slow - understandable; think
what it has to do for joins. So, we built the table on the AS/400, then
copied to SQL Server using the ODBC driver (still called from Java.) The
time went from literally about 5 minutes to about 10 seconds. Since the
process is interactive, the more than an order of magnitude improvement made
the difference between the app being usable and just another dead horse.


Joe Sam

Joe Sam Shirah - http://www.conceptgo.com
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International? http://www.jguru.com/faq/I18N
Que Java400? http://www.jguru.com/faq/Java400

----- Original Message ----- From: "Thorbjoern Ravn Andersen" <ravn@xxxxxxxxxx>
To: "Java Programming on and around the iSeries / AS400"
<java400-l@xxxxxxxxxxxx>
Sent: Wednesday, October 28, 2009 10:14 AM
Subject: Re: Retrieving integer parameter after JT400 ProgramCall?


Loyd Goodbar skrev:

James and Joe,

Other than decoupling the program call by adding another layer, what are
the
other advantages for calling via JDBC? Not to say I won't use the stored
procedure in the future but using ProgramCall appeared straightforward and
I
was 90% there. The last 10% is a bear though.

The work previously mentioned in enhancing PCML should hopefully make
this much, much easier.

Having it work with JDBC means that it will work with any language that
can talk to the database and not only Java. hat may be an advantage or
a disadvantage depending on your view.

Is there any other database connector which can be carried around like
jt400/jtopen or do they all require Client Access installed?