At 18:44 +0200 on 04/30/2013, R.S. wrote about Re: Check whether job
still running:
Another option: JOB1 allocates some dataset with DISP=OLD, the JOB2
also has DISP=OLD for the same dataset. Assuming JOB1 is submitted
first, JOB2 will wait for JOB1 completion.
This solution does not fly. JOB2 will sit there and waste an
initiator until JOB1 (which is long running) ends. You need some
method of preventing JOB2 from even being initiated until JOB1 ends.
Thus the Job Scheduler or JOB1 Submits JOB2 options are ways to go.
If you can live with JOB1 and JOB2 having the same jobname and you
use JES2, that will handle the wait since JES2 will not allow JOB2 to
be initiated so long as JOB1 is executing.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
