I have a simple group job setup that I use for developer tasks. In the
setup program, for each of the jobs I want, I stuff the initiating
command into the Group Data Area (*GDA) then do a TFRGRPJOB to start the
group job, retrieve the *GDA, then SETATNPGM PGM(GRP_ATN), then
TFRGRPJOB GRPJOB(*PRV) right back to the setup program to continue
setting up jobs.
Each group job *is started*, but does almost nothing, since the command
it runs isn't actually executed until the group job is selected from the
menu. The setup program runs quite quickly.
Don't know if that would help you or not, but it appears to be
economical on CPU and memory, since nothing really happens in a group
job until it is picked from the menu.
There's not a lot of code. The significant part of the setup program is
show below.
Sam
/*== Get command to run ============================================*/
RTVDTAARA DTAARA(*GDA) RTNVAR(&GDA)
/*=== Set my own attention program for this job ====================*/
SETATNPGM PGM(GRP_ATN)
/*=== And go right back to caller to continue initialization =======*/
TFRGRPJOB GRPJOB(*PRV)
/*=== Resume here when selected from menu ==========================*/
/* -- Run the command specified in the *GDA */
CALL PGM(QCMDEXC) PARM(&GDA 512)
On 4/27/2017 9:22 AM, Gerald Magnuson wrote:
so we run in our interactive environment, group jobs...
we have our users initial program run a CL that reads a PF and
performs a TFRGRPJOB, looping through all records for that user.
has someone a process in which the group jobs are not spawned until the
user
selects them for the first time?
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
midrange.com
