Basically we have CLASSPATH set to /usr/lpp/smp/classes as the
documentation states. The actual class files being looked for by the
job are in /usr/lpp/smp/classes/com/ibm/smp. What I don't understand is
how SMP knows to look beyond /usr/lpp/smp/classes for the class files.
What is telling SMPE to append com.ibm.smp.GIMJVCLT to the classpath
variable, in the example below?
As Skip mentioned, the class name com.ibm.smp.GIMJVCLT is hardcoded in
SMP/E. However, perhaps your question has more to do with the Java
requirements for class names, application package names, and the
difference between the physical names of class files and the logical
names of the Java application classes.
For example, when starting the JVM, SMP/E tells it to pass control to a
class. This is done not by specifying the phyical file location for
that class, but rather by specifying the class name,
com.ibm.smp.GIMJVCLT. The class name is composed of a Java "package"
name (com.ibm.smp) prepended to the class name (GIMJVCLT). The JVM
translates the class name com.ibm.smp.GIMJVCLT to a physical file with a
relative name of comp/ibm/smp/GIMJVCLT.class, which of course when using
the classpath can be resolved to the real physical file location of
/usr/lpp/smp/classes/com/ibm/smp/GIMJVCLT.class.
Kurt Quackenbush -- IBM, SMP/E Development
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
