×
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.
Hello,
On 4/4/2011 2:46 PM, hockchai Lim wrote:
1) Is there not a way to use java.version property to tell the system to use
the 32 bits version of jvm on a particular job?
Correct, you have to use JAVA_HOME.
Honestly, when I work with Java on other platforms, I've always used
JAVA_HOME to select the version. Never heard of using java.version,
except on IBM i. And now IBM has said that java.version is deprecated,
and we should all switch to using JAVA_HOME.
Since the 32-bit version of Java was written/compiled on AIX (not IBM i)
it sort of makes sense that it wouldn't work with java.version, which
seems to be an i-only feature.
Currently, I've (java.version 1.5) as the PROP parameter value for
the RUNJVA command. When I look at the job log, I see "Java Virtual
Machine is Classic." in the joblog.
Yes, you are using the native ("Classic") JVM instead of the J9
technology (PASE) one.
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.
midrange.com
