RE: Java->RPG, *SERIALIZE required?

Unfortunately, the RPG code is fairly involved.

Thanks



-----Original Message-----
From: Mark Waterbury [mailto:mark.s.waterbury@xxxxxxxxxxxxx]
Sent: Friday, March 06, 2020 12:22 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Java->RPG, *SERIALIZE required?

Justin,


It kind of depends on what the RPG code is doing ...?

If it is a fairly short-running function that returns a value, you likely would never notice that THREAD(*SERIALIZE) is doing anything.  It creates a MUTEX lock to ensure that two threads do not enter the same procedure at the same time.  On return from that procedure, the MUTEX lock is released, allowing the next caller who may be waiting on that MUTEX to have access. (Threads will queue up automatically, FIFO, waiting on the MUTEX lock.)


You can also try THREAD(*CONCURRENT) but you need to read the manuals and understand the nuances of what that really does.  You cannot just stick "H THREAD(*CONCURRENT) on any old RPG code and expect that it will work correctly in a multi-threaded job.


Hope that helps,


Mark S. Waterbury