Create a jobq that only allows 1 job at a time to run
Then submit your jobs to it
...they will just run in that order
The idea of a data area also works pretty well
.....but depending on how you work it, it may need to be maintained if new
jobs are added
The old s36 was good at this, you just had to test whether it was active or
not
....no such animal any more
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Monday, September 12, 2011 6:37 AM
To: midrange-l@xxxxxxxxxxxx
Subject: How do you determine when numerous SBMJOBs have ALL finished
Good morning all
I have one job that submits numerous (a lot) of submit jobs Once ALL of them
have finished SUCCESSFULLY, I need to submit another one (let's call it
PROGRAMLAST) I was just wondering if anyone else is doing or has done the
same thing, what process was used.
I am toying with the idea of using a data area and within each SBMJOB adding
1 to this data area and checking for a particular value in the PROGRAMLAST
program This would mean that PROGRAMLAST would need to be always submitted,
but waiting for a value to appear in the data area
Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
