At 13:39 -0800 on 02/10/2009, Edward Jaffe wrote about Re: JCL job
execution order:
This is easy with JES3; difficult nee impossible with JES2. If the
environment is JES2, I suggest you have the last step of each job submit
the next one.
The simplest method (as others have stated) is to have each job
submit the next (with the last step being a COND=EVEN submission via
INTRDR). You can also place it as the first step IF you have an
IEFBR14 last step with a DD DSN=UNIQUE-DSN,DISP=OLD DD statement to
hang-up the submitted job until the first ends. This IEFBR14 STEP is
not needed IF the jobs are all the same class and only 1 INIT hands
that class.
BTW: There are JES2 SCHEDULER MODS that allow you to designate the
order that the jobs run in just like you can do with JES3.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
