|
Why I am getting this message after I serialized my PCML document using java com.ibm.as400.data.ProgramCallDocument -serialize mypcml Stack trace: java.io.IOException: Not in GZIP format java.lang.Throwable(java.lang.String) java.lang.Exception(java.lang.String) java.io.IOException(java.lang.String) void java.util.zip.GZIPInputStream.readHeader() java.util.zip.GZIPInputStream(java.io.InputStream, int) java.util.zip.GZIPInputStream(java.io.InputStream) com.ibm.as400.data.PcmlDocument com.ibm.as400.data.ProgramCallDocument.loadSerializedPcmlDocument(java.lang. String) com.ibm.as400.data.PcmlDocument com.ibm.as400.data.ProgramCallDocument.loadPcmlDocument(java.lang.String) com.ibm.as400.data.ProgramCallDocument(com.ibm.as400.access.AS400, java.lang.String) com.fc.frontierapps.CheckApplications(java.lang.String, java.lang.String, java.lang.String) void com.fc.frontierapps.Test.main(java.lang.String []) An I/O error occurred. com.ibm.as400.data.PcmlException: An I/O error occurred. java.lang.Throwable() java.lang.Exception() com.ibm.as400.data.PcmlException(java.lang.String) com.ibm.as400.data.PcmlDocument com.ibm.as400.data.ProgramCallDocument.loadSerializedPcmlDocument(java.lang. String) com.ibm.as400.data.PcmlDocument com.ibm.as400.data.ProgramCallDocument.loadPcmlDocument(java.lang.String) com.ibm.as400.data.ProgramCallDocument(com.ibm.as400.access.AS400, java.lang.String) com.fc.frontierapps.CheckApplications(java.lang.String, java.lang.String, java.lang.String) void com.fc.frontierapps.Test.main(java.lang.String []) -----Original Message----- From: Joe Pluta [mailto:joepluta@plutabrothers.com] Sent: Wednesday, April 04, 2001 9:17 AM To: JAVA400-L@midrange.com Subject: 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.