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
