Re: java.version message

[Barbara Morris <bmorris@xxxxxxxxxx>]

On 2/13/2013 10:19 AM, Gerald Kern wrote:
> Thanks for responding Barbara,
>
> I tried Dan's suggestion and as you stated, it did not work.
>
> I reviewed the link you posted but knowing very little about java and its
> role in the RPG environment is quite foreign to me, so the sentence "To get
> rid of that message, just remove the java.version property from
> the RPG environment variable, and from any of the places that Java looks
> for Java properties." is the challenge.
>
> "'The RPG runtime only passes the properties that are specified in the
> QIBM_RPG_JAVA_PROPERTIES environment variable."
>
> I'm confused as to where to populate the "QIBM_RPG_JAVA_PROPERTIES
> environment variable".

You probably don't need to use the QIBM_RPG_JAVA_PROPERTIES environment 
variable. If you aren't already using it, I don't think there's any 
reason to start using it.

So if WRKENVVAR doesn't show QIBM_RPG_JAVA_PROPERTIES in the job where 
you are seeing the message, then don't worry about it. Instead, look at 
the Java page 
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=%2Frzaha%2Fsysprop.htm 
where they talk about the various places you can specify properties.

- For the first bullet, if you don't have the QIBM_RPG_JAVA_PROPERTIES 
envvar, the other possibility is that your application is calling the 
invocation API directly, rather than letting RPG do it. Look for a call 
to JNI_CreateJavaVM().
- For the bullet about QIBM_JAVA_PROPERTIES_FILE, check for that envvar 
in the job getting the message
- For the bullet about SystemDefault.properties, check the user profile 
to see where the home directory is, and look in that directory for that 
file.
- For the final bullet, see if that file exists.

Ironically, the RPG environment variable was added specifically to 
handle the java.version property, since at the time, the java.version 
property was ignored when it was found in Java's 
SystemDefault.properties file. Java eventually started to honour the 
java.version property when found in the SystemDefault.properties file, 
so all Java properties could be specified in any of the places that 
either RPG or Java looks for properties.

The only real reason to use the RPG environment variable now is that it 
has the highest priority in the case of the same Java property being 
specified in multiple places. So if SystemDefault.properties has a value 
for property X, say X=a, and QIBM_RPG_JAVA_PROPERTIES has a value for 
property X, say X=B, then the RPG one will win, and the value for 
property X will be B.