Ideally this is best done with a job scheduler or an automation product. But the sometimes bureaucratic red tape that surrounds those can be a pain for one off type work.
You could set it up so that each job, in its last step, submits the next job. That should help assure that they run in the order you want. -- Don Imbriale On Thu, Apr 14, 2011 at 8:20 PM, Patrick Welsh <[email protected]>wrote: > Hi Mainframe Gurus, > > Perhaps you can help a Lowly trainee out. > > I have a situation where I want to submit 12 batch jobs in order, with an > MVS command to bring a volume online between jobs 2 and 3. > > I could ask Ops Support to use the automation product to set up some rules > for this, however as a training exercise I was looking to do it without > using Control. > > I can get the jobs to submit in the correct order by using the INTRDR, but > this does not wait untill one job is finished before the next starts. > > Ideally I would also like to trap the return code of the previous job and > use this to conditionally submit the following job or halt the process. > > Can you offer any advice on the best method/tools to do this and point me > in the direction of the appropriate doccumentation. > > ---------------------------------------------------------------------- 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
