On an individual user basis, the easiest method on a V2.3 system or higher is to use the new JOBGROUP feature.
//JOBT JOBGROUP ERROR=(RC>4),ONERROR=FLUSH //JOBA GJOB //JOBB GJOB // AFTER NAME=JOBA,WHEN=(RC=0) //JOBC GJOB // AFTER NAME=JOBB,WHEN=(RC<=4) //JOBD GJOB // AFTER NAME=JOBC,WHEN=(RC=0) //JOBT ENDGROUP _____________________________________________________________________________________________________ Dave Jousma AVP | Manager, Systems Engineering Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI 49546 616.653.8429 | fax: 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Steve Smith Sent: Wednesday, April 15, 2020 9:36 AM To: [email protected] Subject: Re: Order of execution for nearly-identical batch jobs with the same name **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** The OP's question was just curiosity. That question was answered. He didn't ask *how* to schedule jobs to run in order. Anyway, 2/3 of the ways listed do *not* guarantee execution order (in fact they have no effect at all on a series of jobs with the same name). And multiple systems can affect the order, but that is not the main reason jobs run "out of order". sas On Wed, Apr 15, 2020 at 9:19 AM Allan Staller <[email protected]> wrote: > JES job number is unique (guaranteed). > > Absent son other priority mechanism, jobs are selected FIFO with job class. > > Jobs are queued at the end of conversion. This is unique to (at least) > 1 /100th sec. > If there are multiple converters, each is dispatched uniquely and my > finish a few 1/00ths of a sec. apart. > > This has been the same since the days of HASP/OSMVT. > Using the example below (unique jobname) there are 3 ways to guarantee > execution order. > 1) single initiator for that job class > 2) use WLM managed inits > 3) have job #1 submit job#2 .... > > The reason is that in a JES2 MAS, a job may be submitted on MVSA,, > converted on MVSB, interpreted on MVSC and executed on MVSD. > > HTH, ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN **CAUTION EXTERNAL EMAIL** **DO NOT open attachments or click on links from unknown senders or unexpected emails** This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
