Re: Retrieving integer parameter after JT400 ProgramCall?

Joe Sam Shirah skrev:

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.

Yes, I mean the "carry SQL command with parameters to database, and return result to caller" technology which is named JDBC in the Java world, ODBC in the WIndows world (if it hasn't been replaced with something else).

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.

You still need the ODBC driver. The JDBC driver is special because it is 1) open source and 2) does not require some IBM product to be installed on the host. I am doing a simple project where this is an important parameter as it allows us to do web start clients to casual users hence the interest as we have several .NET-clients who would like us to cater to some of their needs.

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.

I do not know of Samuel Johnsons dancing dog, so this analogy is a bit lost on me. If I understand you correctly, you simply build one place, and move the data elsewhere to make it faster? Is this the fault of the database driver, the network or the database itself? Or is the benefit of running the database on the same hardware as the application so big that the DB2/400 could not compete?