I have developed a test application that successfully
fetches an EJB from a WebSphere 6.1 server using either the
IBM SDK50 or SDK60 when in the development environment;
however, when compiled, said application fails to load the
JVM.

I've been through every related thread in this discussion
and have double and triple checked all of the environment
and registry settings and still no joy.  That said, if I
clear the JDK directory (and all subdirectories), and
overlay it with the JDK14 that came with PowerBuilder
(currently running 10.0), the application has no problem
starting the JVM.  So, unless I'm missing something, the
various registry settings and environment variables must be
set correctly or the JVM in the JDK14 wouldn't successfully
start.  Yes, no?

In all cases I have the java implementation stored in the
default C:\Program Files\Sybase\Shared\PowerBuilder\jdk14
directory.  By simply changing out the contents of the
..\jdk14 directory with various JDKs and SDKs, I get the
following results:

Development environment:
Sybase sourced JDK (1.4.0): JVM starts, however, Lookup
fails.
IBM sourced SDK50 (1.5.0): JVM starts and application works.
IBM sourced SDK60 (1.6.0): JVM starts and application works.

Compiled / Runtime environment:
Sybase sourced JDK (1.4.0): JVM starts, however, Lookup
fails.
IBM sourced SDK50 (1.5.0): JVM fails to start.
IBM sourced SDK60 (1.6.0): JVM fails to start.

Is there something about the runtime environment that
prevents any IBM SDK version of Java from running?

Thanks in advance for your help in this matter.