RE: *INLR

Thanks everyone for your thoughts on how to rewrite this but unfortunately,
the logic was only an example to show the program flow.  Because of how the
system is written and what needs to be done, PgmA submitting PgmB as
individual jobs is the only solutions without spending a ton of hours doing
code rewrite.

I think that I have my answer in that *inlr being on or off really makes no
difference because when the job ends, everything from PgmB gets cleaned up
either way.  Feel free to correct that if I misunderstood some of the
explanations.



-----Original Message-----
From: [email protected] <[email protected]> 
Sent: Wednesday, April 15, 2026 4:48 PM
To: Midrange RPG List <[email protected]>
Subject: *INLR

If I have PgmA and it repeatedly calls PgmB, I know not setting on LR makes
the process faster because it doesn't have to reload PgmB into memory every
time.  

The argument that we are having is related to PgmA submitting PgmB to enable
multi-thread processing.  Does not setting on LR help in this case because
they are different jobs?

For example,
PgmA
	Do until shutdown
		Read Invoice Header File for unprocessed invoices
			If a new invoice is found
				Mark the invoice as In-Process
				Submit PgmB to process the invoice


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


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

Please contact support-FMtJrHiV//lnDLsaKlm4mFaTQe2KTcn/@public.gmane.org for any subscription related questions.