Re: Impact of control option thread(*concurrent)

On 2019-03-15 4:10 AM, Niels Liisberg wrote:

Also notice how you use it: If you call "not treadsafe" stuff like old RPG
programs, some CL commands, where you create temporary stuff in QTEMP etc.
- The you HAVE TO use *SERIALIZED. What it does is simply making a lock
that will remain locked until the procedure terminates - allowing you to
make all the non-thread safe stuff.

You could also have a procedure with the SERIALIZE keyword in a THREAD(*CONCURRENT) module.

But either way, you'd have to ensure that using that THREAD(*SERIALIZE) module or that procedure with the SERIALIZE keyword is the _only_ way to do the non-thread-safe stuff.

For example, if there's a possibility of two different THREAD(*SERIALIZE) modules calling an old RPG program, then those calls would not be thread-safe.