One way to ensure the order of execution would be to have each job have a last step that submits the next job in sequence. If you submit 50 jobs with the same to the internal reader, they get put into the input queue in the order they come out of C/I processing, not in the order they hit the internal reader.
=============================================== Wayne Driscoll Omegamon DB2 L3 Support/Development wdrisco(AT)us.ibm.com =============================================== Dave Salt <[email protected]> Sent by: IBM Mainframe Discussion List <[email protected]> 02/10/2009 03:29 PM Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject JCL job execution order I'm trying to help someone create a process that will automatically submit several jobs at a time. For example, it might submit 20 jobs right after each other, with only a fraction of a second between each job. It's very important that the jobs execute in the same sequence in which they were submitted. For example, if the automated process submits jobs AAA, BBB and CCC, then job AAA must finish executing before job BBB begins to execute (and so on). I was under the impression that I could force jobs to execute in the desired sequence by simply using the same job card for each job. For example, if every job began with this job card: //useridX JOB Then all of the submitted jobs would have the same job letter (i.e. 'X'). As far as I know this means only one of the jobs would execute at a time. What I'm less sure of is that job AAA would be guaranteed to start executing before job BBB? For example, if job AAA is submitted a fraction of a second before job BBB, and both jobs have the jobcard shown above, is it guaranteed that job AAA will start executing first? If it's NOT guaranteed, is there some way to force the jobs to execute in the same sequence as they were submitted? Note that: 1) It doesn't matter if job AAA is successful or not. All I want is to ensure that job BBB doesn't start executing until job AAA has finished. 2) It would be difficult to combine the jobs into a single job; i.e. it is preferable to submit each job separately. 3) These are not production jobs; i.e. they are jobs being submitted on an irregular basis by a user. The user does not have access to any kind of job scheduler. Thanks in advance for any suggestions! Dave Salt SimpList(tm) - try it; you'll get it! http://www.mackinney.com/products/SIM/simplist.htm _________________________________________________________________ The new Windows Live Messenger. You don’t want to miss this. http://www.microsoft.com/windows/windowslive/products/messenger.aspx ---------------------------------------------------------------------- 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
