I just found this in the midrange java archives (did not see it
before)

I will try this and see if I can figure out something:

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?topi
c=%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.





-----Original Message-----
From: John Allen [mailto:jallen@xxxxxxxxxxx]
Sent: Monday, December 21, 2015 2:02 PM
To: java400-l@xxxxxxxxxxxx
Subject: Java error on 7.1 not on 6.1



I have been running a java program on 6.1 for a year or so.



Now I try to run the program on 7.1 and I get this error:

(The java program finishes executing and works fine, but the message
is obviously unacceptable to the users)



Error:

The java.version property was detected as input. This property is used
as output only and has no effect on JVM initialization.

The java.version property was detected as input. This property is used
as output only and has no effect on JVM initialization.

The java.version property was detected as input. This property is used
as output only and has no effect on JVM initialization.

The java.version property was detected as input. This property is used
as output only and has no effect on JVM initialization.



There must be a setting I am missing somewhere but I don't know where
to look/what to change



Thanks



John







--
This is the Java Programming on and around the IBM i (JAVA400-L)
mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/java400-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.