Re: *INLR

Another solution - even if it is not the easiest - would be to create lightweight Threads instead of more heavyweight Jobs.

Multi-Threading with the Pthreads APIs is not so hard, but needs proper planning.

As a primer I wrote a small blog post some time ago:

- https://blog.qpgmr.de/2024/01/19/multi-threading-ile-rpg.html

Regards,
Daniel

Am 16.04.2026 um 01:40 schrieb Barbara Morris <bmorris@xxxxxxxxxx>:

On 2026-04-15 4:48 p.m., smith5646midrange@xxxxxxxxx wrote:

...
PgmB
Process invoice based on invoice number received
Mark invoice as Processed
** Note: no *INLR logic here
Return
VS
Process invoice based on invoice number received
Mark invoice as Processed
*inlr = *on
Return

If PgmB is the only thing that runs in a submitted job, the only difference with ending LR-on or LR-off is the timing of when the files are closed.

Setting on LR within the program means that files get closed explicitly by RPG. Returning with LR off means that files get closed by the system when the activation group ends (due to the job ending).

I don't know which is faster, but my guess is that the difference (either way) is tiny compared to the cost of starting the new job and doing the actual work of the program.

--
Barbara

--
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@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.