Someone else has already suggested debugging this with 'strace' - I'd like to second that motion. It is an excellent tool for finding out where an application (installer) is looking for the files it needs. Simply run 'strace -o strace.log <yourapp> <yourargs>' and wait for it to complete. Then examine the output file 'strace.log' to look for failed attempts to open files. This should give you the clues you need to validate your environmental variable settings, and to verify that you actually have installed the prerequisite binaries.
Regards, Mark Vitale [email protected] On 3/25/13 7:47 AM, "Chase, John" <[email protected]> wrote: >> -----Original Message----- >> From: Linux on 390 Port On Behalf Of Emmett O'Grady >> >> You can set it as: >> >> JAVA_HOME=/opt/somejava/version >> >> And PATH=$JAVA_HOME/bin:$PATH > >Actually, what I meant to say is that we've tried it with both $JAVA_HOME >and $JAVA_HOME/bin in the PATH variable (at the same time). We've tried >it with the pathnames "spelled out" as well. > >We don't explicitly set CLASSPATH, because since we have only the one jre >installed, it's not supposed to be necessary. I guess we'll try setting >CLASSPATH next, and if that doesn't work we'll probably go get the IBM >Java SDK for s390x and try that. > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
