Re: CLASSPATH for Qshell

Justin,

This is the response I have from a similar PMR from the QSHELL folks:

Customer must have a /Qibm/userdata/java400/SystemDefault.properties file
with the line java.class.path=.:/java  in it.  This is forcing the
classpath to exactly that value which does not include the tools.jar.
That's why the javac command will not run.  It is also possible that this
hardcoded java.class.path is preventing your rmtqshell.jar from being
found.  They need to remove any java.class.path=xxx from the
SystemDefault.properties file.

If the customer needs to set a global classpath, it is better to set the
CLASSPATH env var.



Hope that helps.


Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab




wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/27/2007 03:19:56 PM:

I am receiving the following when I try to open a Qshell in WDSc:

java.lang.NoClassDefFoundError:
com/ibm/etools/iseries/core/server/rmtshell/RmtShellServer
   at java.lang.Throwable.<init>(Throwable.java:196)
   at java.lang.Error.<init>(Error.java:49)
   at
java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:40)

I believe that it is a CLASSPATH issue.  We recently added a
"java.class.path" property to our global SystemDefault.properties file
and that is when I started having this problem.  My thought is to
specify the CLASSPATH in my personal SystemDefault.properties file, but
I do not know what the CLASSPATH should be for Qshell.

I5/OS   v5r4
WDSc    6.0.1   Build id: 20050725_1800
Java    1.5