I've been told since I got into this field that the answer is that it's basically random. I just read the post from another responder (forgot who, and deleted his post) pointing to the JES2 manual. I followed the logic flow of the even and odd converters but they pretty much imply it's random as well. It depends on what resources are needed versus available at job conversion time.
So, now that I know more about how it works, it's still in essence, random. Rex -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Farley, Peter x23353 Sent: Tuesday, April 14, 2020 3:00 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: [External] Order of execution for nearly-identical batch jobs with the same name I have been confused by this behavior in z/OS for a long time now. Can anyone explain to me how JES2 selects which job will be executed next from a set of identically-named jobs at the same priority level in the same job class? Recently observed behavior has been all over the map. E.G., today I submitted four jobs from TSO all with the same job name. Each was assigned a sequential job number, like this: TSOUSERM 1001 TSOUSERM 1002 TSOUSERM 1003 TSOUSERM 1004 Observed execution order was: TSOUSERM 1004 TSOUSERM 1002 TSOUSERM 1003 TSOUSERM 1001 On a different day I saw that the order executed was third, second, fourth, first. These jobs execute the same number of PROC's and programs in the same order just using a different initial input file name. They are identical in every way except for the input file name. Why are these jobs not executed in the order submitted? That I guess is what I really don't understand. Fortunately I don't *need* them to execute in a particular order, I just don't understand why they do NOT execute in submission order. TIA for curing my ignorance. Peter -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
