On Fri, 23 May 2008 04:25:10 -0400, David Cole <[EMAIL PROTECTED]> wrote:
>Hi, > >I have a process that submits up to a couple of hundred jobs for >execution. I require that these jobs execute in the same order in >which they were submitted. > >For decades I have accomplished this by assigning all of the jobs to >a specific job class and then insuring that there was never more that >one initiator that had that job class assigned. > >I am now running at a new data center. (Guess where...) And I have >just discovered that my jobstream is running out of sequence. For >some reason, my single-threading initiator is selecting jobs from the >input queue out of sequence. > >Is there an "official" way to enforce job execution sequencing? > >TIA > >Dave Cole REPLY TO: [EMAIL PROTECTED] >Cole Software WEB PAGE: http://www.colesoft.com >736 Fox Hollow Road VOICE: 540-456-8536 >Afton, VA 22920 FAX: 540-456-6658 > >---------------------------------------------------------------------- For the longest time before we moved the application to a scheduler we had a similar situation where we had one jcl deck that contained hundreds of jcls within the one deck. We also had the need to run these in the order they were submitted and we got around this by simply setting the priority of all input jobs to be the same priority ($TJ1-9999,P=10) which meant that all the jobs ran in the order we needed. It could be further qualified to specify a job mask $tJ1- 9999,JM=MYJOBS* if needed. It wasn't ideal but it worked for us for several years. Best regards, Gil. ---------------------------------------------------------------------- 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
