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



Thanks for the suggestions and the logic!

Now, does anyone know of a way to determine which version is going to be used? I don't think it automatically uses the highest version (am I wrong?) It seems to be different based on version, release, and modification of OS400.

I guess I could find out what the default is for each VRM of OS400 and add logic to the script to take this into account. Then I would also have to look for the existance of .props files (I forget the location and names right now) that could also determine which version is going to be used. I was just hoping there was an "easier" way to tell.

Thanks,

Ken


Bruce Jin wrote:
You can try these two methods:

1. In CL check the folder existence to decide if a particular JDK version is installed. E.g. /QIBM/ProdData/Java400/jdk14 is the location of JDK 1.4. 2. If you call qshell scripts in CL you can check installed JDK using something like this:
jdk14=/QIBM/ProdData/Java400/jdk14
jdk13=/QIBM/ProdData/Java400/jdk13
jdk12=/QIBM/ProdData/Java400/jdk12
if cd $jdk14
  then jv=4
elif cd $jdk13
  then jv=3
elif cd $jdk12
  then jv=2
else
  echo Connot find $jdk12 or $jdk13 or $jdk14!
fi
jdk=/QIBM/ProdData/Java400/jdk1$jv
echo Found JDK 1.$jv, use $jdk.
export -s JAVA_HOME=$jdk

I hope someone has better ways to do this.

Bruce



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.