Activation Group design question

I have program clle_1 currently in pilot, and am reviewing activation
group design to get correct function with good efficiency.

One concern is file updates made by program sqlrpgle_1 must
be read by programs sqlrpgle_2 and sqlrpgle_3.



clle_1 runs as a (almost) never-ending program, meaning it
runs in a loop for about 24 hours, ends and re-starts minutes later.

The clle_1 loop has two phases, separated by DLYJOB(75) :


1) Call sqlrpgle_1 to collect pallet item and quantity picked from
a 3rd-party app running on our network and update custom files
on our system i. Data from the 3rd-party app is received from
IFS directory 3p_1.


Call sqlrpgle_1 to collect pallet load status from the 3rd-party
app and update custom files on the i to show pallets confirmed
for shipment. Pallet confirmation is received from the same
3rd-party app, but the data is received from IFS directory 3p_2.



DLYJOB(75)


2) Call sqlrpgle_2 to check for customer deliveries where all pallets
are confirmed for shipment (no updates) and call sqlrpgle_3 to
load local files with delivery data, print pallet labels and transfer
an Advance Ship Notice to the customer.

DLYJOB(75)


My new activation group design:

Leave clle_1 set to *DFTACTGRP

Change sqlrpgle_1 from activation group QILE to *NEW
(to force updates to be "posted", assuming that with a *NEW
activation group, when sqlrpgle_1 returns with LR=*ON, file
updates "take effect" similar to FEOD ?)

Change sqlrpgle_2 from activation group *NEW to *CALLER,
Different than the *NEW activation group created by sqlrpgle_1,
for same reasons mentioned for sqlrpgle_1.

That is a combined total of some 1,400 activation group create/delete steps per day.

All suggestions/comments gratefully welcomed . . .