Re: Staring the JVM 32 bit version

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

hi Paul,

Do you have OS400_JVM_12 defined?  Are you using the 1.2 version of the 
JNI specs?  Or are you still using the legacy support?

I have to admit that I haven't tried starting the JVM manually with 
recent releases.  I just let RPG start it for me, it does all sorts of 
extra code to handle classpath, qibm_rpg_java_properties, 
SystemDefaults.properties, et al... never saw any point in rewriting 
that myself.

But in the days when I did start the JVM manually, I know you were very 
limited in your capabilities if you didn't use the 1.2 version of JNI. 
Using the older version always seemed problematic.


On 8/23/2010 10:14 AM, PAPWORTH Paul wrote:
> I'm using JNI_CreateJavaVM  to start the JVM and this works fine on one
> machine with the Java_Home environment variable set as follows
>
>
>
> Value . . . . . . . . . :   '/QIBM/ProdData/Java400/jdk15'
>
>
>
> However on  the test machine with this variable set to the 32 bit
> version
>
>
>
>
>
>
> Name  . . . . . . . . . :   JAVA_HOME
>
>
>
>
>
>
>
>
> Value . . . . . . . . . :   '/QOpenSys/QIBM/ProdData/JavaVM/jdk50/32bit'
>
>
>
>
>
>
> The API  falls over with a return code of  -3 (Version error) . does
> anyone know what needs to done for this to work. Funnily if I let the
> o/s start the JVM (first call to a Java) all works well.
>
>
>
>
>
> Thanks in advance