Re: Java->RPG, *SERIALIZE required?

I might quibble with the assertion that you "must" thread(*serialize) in
that a lot of Java processes are single threaded; No need to serialize in
that case. Also it is conceivable that one could write RPG code that didn't
require *serialized access. But on the whole, thread(*serialize) is good
advice, in that it ensures safe access to the RPG code from multi-threaded
callers.

Now I'm curious why you believe that thread(*serialize) might be
undesirable in your current project?



On Fri, Mar 6, 2020 at 10:34 AM Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

I have an old reference (2002) that says you must specify
THREAD(*SERIALIZE) when calling an RPGLE service program from Java. Is
that still required/recommended?

The RPG Ref manual explains that THREAD(*SERIALIZE) prevents multiple
threads from concurrently access the same code, in essence making it
singe-threaded. This would be undesirable for my current project.


TIA
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com