Our Situation:

We have a Cobol JVM for Eclipse project packaged as a jar file. We have another Cobol JVM for Eclipse project packaged as another jar file.  We currently have these deployed with no issues. We,however, now have to open up one of these to make a small code change.  The first jar uses a shared program in the second jar.  The method we have used is the "CALL 'programname' USING " syntax.  

The directives we are using on the jar when building are these:

IDXFORMAT"3"
SQL(DBMAN=JDBC TARGETDB=ORACLE BEHAVIOR=UNOPTIMIZED CLOSE_ON_COMMIT=NO NOCHECKSINGLETON DATE=EXTERNAL OPTIMIZECURSORS=NO)
ILUSING(packagename of called program)

our calling jar project compiles just fine but when i export it as a jar it fails on runtime with error 173 called program/file not found.

Both the called jar and calling jars exist in the same directory and this directory is added on the CLASSPATH.  what would i be missing here?

Hello Christopher,

Please try adding the full filespec for each of the .jar files to the CLASSPATH, rather than just specifying the directory that contains them.

full filespec?  do you have a quick example

Assume that you have built myjar1.jar and myjar2.jar, and these have been placed in the directory c:\\apps\\jarfiles.

You might try adding the jar files to the CLASSPATH with: