Re: QRPLOBJ objects in use?

Hi David,

we use our in-house x-reference database - which we update whenever a program gets into production.

And I have written a service-program which does a recursive collection of all programs and service programs used by the caller - also the programs and service programs which are used by called programs or procedures - and so on until we end with an complete list. The procedure then stores all those in an array together with the last changed date from the object.

// start of long running batch job
collectReferences(psds.pgmName);

Later in the program we only check this array again against the objects itself:

if collectedReferencesChanged(psds.pgmName);
rtcode = 'RC'; // -> signal a re-call to the CLLE
*inlr = *on;
return;
endif;

This way, the heavy lifting (with the recursive collection of all references) is only done at the program start. The largest program we have has about 420 references in a tree that is about 10 calls deep - many of those references are of course duplicates, which are eliminated when storing all info in that static array in my service program.

As my service program uses our own in-house x-reference, it wouldn't help you so much, but I think you get the idea.

HTH and kind regards,
Daniel

Am 27.02.2026 um 16:57 schrieb David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:

On Wed, Feb 25, 2026 at 3:37 PM Daniel Gross <daniel@xxxxxxxx> wrote:

probably they're replacing service programs or programs in production -
now you want to know, which jobs have to be restarted, to "re-load" their
service programs or program objects.

Yes, exactly that.

Specifically, we have many web services running through IWS and we never turn
on lr so the programs stay active (very high volume, so we avoid having to
open & close files).

david
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.