Re: Differences between calling Java from Qshell and RPG?

"McCully, Keith (RBS Insurance)" wrote:

Also, saw an IBM FAQ that states that this exception could be caused if the
environment variable QIBM_MULTI_THREADED was not set. However, I had already
set this via ADDENVVAR:

http://www-304.ibm.com/jct09002c/isv/tech/faq/individual.jsp?oid=1:88404

This seems to agree with my earlier thoughts that this was an environmental
problem relating to the RPG call environment since the class runs ok and
sends the MQ message when called from Qshell.

Barbara:
I did a DMPJVM for both environments as you suggested but couldn't see any
differences.
I'm wondering whether upgrading to jvm 1.4 would benefit but the classes
appear to run ok at jvm 1.3 when running from Qshell?

I don't know, but in my experience, problems related to the java version
are caused by the JVM created by the java command being say 1.4, while
the JVM created by the JNI invocation API (RPG call to Java) is say
version 1.3.  If both are 1.3, I doubt that the version is the problem. 
(But I don't know anything about those classes, so take that with a
grain of salt.)  

I wonder if there's more to the multi-threaded issue than just the
environment variable.  On IBM's info center, I only find
QIBM_MULTI_THREADED mentioned in conjuction with qsh, so maybe it's
irrelevant for jobs not started by qsh.  For example, 

   QIBM_MULTI_THREADED (Start multi-thread capable processes)
       This variable determines if processes started by qsh can create 
       multiple threads. When the value of the variable is "Y", all 
       child processes started by qsh can start threads. The default 
       value is "N".

How about invoking your RPG program as a qsh command?  (That would start
a new job.)
   QSH CMD('/qsys.lib/mylib.lib/mypgm.pgm')