Re: You Got To Love Troubleshooting RPG calls To Java using

Richard,

I found a thread on the JAVA400-L list archives where you delineated your travails. I empathize. Maybe this problem has something to do with the latest 7.1 technology refresh. It appears to be isolated to the RPG => Java interface. There must be some recipe for setting the environment that will allow RPG to properly launch a JVM within the job and create a native interface. But that recipe appears to be a secret.

On our server there appear to be at least 3 versions of Java. That's what I suppose by the three (3) drectories:

/jdk50
/jdk60
/jdk626

And there appears to be /32bit and /64bit versions within each of those directories. There appears to be even more versions within /bin and /jre/bin directories underneath. With all those versions of Java, even IBM may be getting confused about how to launch a correct version of Java from an RPG program.

-Nathan.





----- Original Message -----
From: Richard Schoen <richard@xxxxxxxxxxxxxxx>
To: "rpg400-l@xxxxxxxxxxxx" <rpg400-l@xxxxxxxxxxxx>
Cc:
Sent: Sunday, August 19, 2012 12:21 PM
Subject: RE: You Got To Love Troubleshooting RPG calls To Java using

We recently abandoned our 1 RPG program that was written this way as we had a similar problem when a customer upgraded.

Spent a week messing around to no avail.

In our case we re-engineered the entire program as a Java class.

Personally I like this better anyway as you can wrap Java class calls with a CL quite easily.