Re: Impact of control option thread(*concurrent)

This is just my opinion but I think it is absolute insanity to be using
multi-threading in RPG. It just isn't built for it. That is one of the
reason why I think we need a clean spec language (which I know will never
happen).

It increases the size of the program because it has to include all the code
for multi-threading. You make every program multi-threaded and what happens
when somebody down stream makes some change without consideration for
multi-threading. Russian Roulette.

On Tue, Mar 12, 2019 at 12:30 PM Mihael Schmidt <mihael@xxxxxxxxxxxxxx>
wrote:

Hi,

I was wondering if there is any significant overhead by (or reason
against) compiling all RPG programs and service programs with
THREAD(*CONCURRENT)?

Usually I only have the constellation that only one thread per job is
created. Though when using frameworks like ILEastic multiple threads per
job are used. Then every program/service program in the call chain
should support multithreading.

I am grateful for every info or opinion.

Best regards

Mihael

--
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