× 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.



>From our PCML expert ...

   In V5R1, we made a change to the serialization logic for performance.
   Prior to V5R1, we zipped the serialized PCML.  Loading serialized PCML
   was slower than parsing PCML source.  We found that we were getting
   killed by the performance of unzipping the serialized PCML.  Since most
   people ship the serialized PCML in their jar (which is also zipped), we
   decided it cost too much with no benefit to also zip the serialized
   PCML.  It looks to me like what happened here is that the PCML was
   serialized with V5R1 but was loaded with older PCML code.

David Wall
AS/400 Toolbox for Java




                    "Tanveer,
                    Mohammad"                To:     "'JAVA400-L@midrange.com'" 
<JAVA400-L@midrange.com>
                    <MTanveer@friedman       cc:
                    corp.com>                Subject:     RE: ProgramCall and 
ProgramParameter classes
                    Sent by:
                    java400-l-admin@mi
                    drange.com


                    11/02/2001 12:08
                    PM
                    Please respond to
                    java400-l





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
+---
_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.







As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.