Complex answer. See this link (for 2.2):
https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.hasa300/has2v5_Job_selection_and_execution.htm
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM comming son  *




On Tue, Apr 14, 2020 at 11:00 PM Farley, Peter x23353 <
[email protected]> wrote:

> 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 [email protected] with the message: INFO IBM-MAIN
>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to