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 > Schedrun? :-) Are you allowed to modify this system? If so, what about the Mellon Bank JES2 modes (/*AFTER, /*BEFORE, etc.). We still use those, but though ThruPut manager. Otherwise, a sure fire way is to have one job submit the next. This has been discussed before, search the archives. Cheers, Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
