RE: ProgramCall and ProgramParameter classes

This is excellent.  When I get back from my honeymoon, I plan on doing some 
performance tests to compare the various methods of getting data from the 
AS/400 in Java.  Here are some of the methods I see:

1. Calling a program via ProgramCall
2. Calling a program via PCML (though I don't use this much)
3. Calling a program through a JDBC CallableStatement
4. Direct data queue access
5. Direct file access via JDBC, native and non-native
   (what's a better term for "non-native", folks?)
6. Direct file access via toolbox drivers

Can anybody think of others?  Should I include JINI on the list?


> CallableStatement has a getBytes() method to get the output data as
> a byte array.  You should also change the way you register the output
> parameter (call it a varbinary instead of a char, for example).
> CallableStatement is a core part of JDBC so this should be very
> portable.

I'm not quite sure I understand this, David.  What's a "varbinary", and what 
are its advantages/disadvantages as opposed to a character parameter?

Joe

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