by Robert Sample » Sat Jun 24, 2017 4:14 am
There are only two ways to accomplish this;
1. Use a job scheduler and put a dependency on JOB2 to run after JOB1
2. Make sure that class L is assigned to only one initiator and submit JOB1. Once JOB1 starts executing, submit JOB2. If you submit JOB1 and JOB2 without verifying JOB1 has started executing, it is entirely possible for JOB2 to start executing before JOB1.
JES explicitly states that merely submitting JOB1 before JOB2 does not ensure that JOB1 will execute before JOB2 even if they are in the same job class. And if the two jobs are in different job classes, they may well be assigned to different initiators so JOB2 could run before JOB1, while JOB1 is running, or after JOB1.
And terminology is critical in IT, where similar terms may have very different meanings. None of this has anything to do with the job PRTY= option which may (or may not -- JES2 may ignore the option depending upon how the site is set up) be used on the JOB statement to control job processing priority. Using a post title of "set job priority" is very misleading about what you want to do.