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


  1.  Home
  2. JAVA400-L
  3. November 2008

Re: Java and V6R1 Odd Problem?

James Perkins skrev:
Thorbjørn,
Thanks! Sure enough when I run your code without the -D argument, I get "
java.vm.name=IBM J9 VM". When running with an override to the version I get
"java.vm.name = Classic VM". I must have missed that somewhere in the
documentation.

I really like the way that IBM has implemented Java on the i with a single command, which invokes the appropriate binary. As opposed to the Sun way of a zillion versions all of which get installed somewhere differently and with no shortcuts what so ever (so your JAVA_HOME environment variable break from time to time).

Then again I like the way that WSDCi can use its own _certified_ JVM without subtly breaking when you update.

Can't have it all :)
Looks like it's time to go back and do some more reading ;-)

Nah. Code should be selfexplanatory :)

Did you note that PropDump listed the properties alphabetically? Can you see how? ;-)

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
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.