On 7/17/2010 6:10 PM, Thorbjoern Ravn Andersen wrote:
I know, but I belive that if a given scenario is "you are running CCSID
5026, and the Classic JVM has a show stopper bug acknowledged by IBM
which is fixed in the J9 one" that might a good reason for the customer
to consider installing an extra JRE.

The fact that they have to install a JRE to use this particular feature of our product was hard enough a pill to swallow to begin with. :)

Question is, what code do you have that essentially locks you with the
Classic JVM?

None. But we try to minimize the number of LPP's that we require a customer to install.

I want the java app to run with the classic and J9 JVM's. It works fine in CCSID 37 & 5035. CCSID 5026 is the only one we've encountered a problem with.

As it happens, I'm working around the problem by changing the CCSID to 5035 if they are running 5026, run the Java application, then switch back to 5026.


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