Re: Excel/POI - Please Help The Drowning Man

Jon Paris wrote:

That requirement relates to the RPG runtime not being threadsafe Bob.  So I
think it is only relevant when you are setting up an RPG procedure to be
called as a native method or when you are calling a Java method which may
subsequently call an RPG native method.

When you are simply calling Java methods I don't think it is an issue.

Thread issues can go beyond the static storage in an RPG module,
although that's all that THREAD(*SERIALIZE) protects from multi-thread
access.  I think it's a good idea to be aware of thread issues when
calling Java, and coding that keyword should raise the consciousness a
bit.  But you are right that if the called Java methods will _never_
call back to any native method, then there is no need to protect the
static storage in the module from access by multiple threads.

I do think the single threading in the job stream may be an issue though - I
think the JVM is effectively run in a separate job.

Not sure what you mean here, Jon.  If RPG calls Java using
EXTPROC(*JAVA), the JVM is in the same job as the RPG program.