/bin/classic or /bin/j9vm for JDK1.5

General discussion on the JZOS batch launcher and toolkit
Post Reply
Cogito-Ergo-Sum
Posts: 30
Joined: Thu Jan 25, 2007 8:31 am
Location: Bengaluru, India

/bin/classic or /bin/j9vm for JDK1.5

Post by Cogito-Ergo-Sum »

Hi,
This is an excerpt from the STDENV DD name in the sample job for using Batch Launcher :

Code: Select all

###########################################################
# Customize below to match your installation:              
# JAVA_HOME - The location of the SDK                      
# JZOS_HOME - The location of the JZOS alphaworks preview  
###########################################################
export JAVA_HOME=/MVSPP/lpp/java/J5.0                      
JZOS_HOME=/u/S611204/jzos                                  
                                                           
export PATH=/bin:"${JAVA_HOME}"/bin:                       
                                                           
LIBPATH=/lib:/usr/lib:"${JAVA_HOME}"/bin                   
LIBPATH="$LIBPATH":"${JAVA_HOME}"/bin/classic              
LIBPATH="$LIBPATH":"${JZOS_HOME}"                          
export LIBPATH="$LIBPATH":                                 
However, I notice that, for SDK 5.0 (for 64-bit as well) the libjvm.* files are stored at $JAVA_HOME/bin/j9vm and libjvm.so only is at $JAVA_HOME/bin/classic.

What is the difference between the two apart from IBM 64-bit SDK for z/OS, V5 - Restrictions and Other Considerations (See 'Migration' heading) ?

BTW, I have had no issues with /bin/classic.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
--Sherlock Holmes
Post Reply