In <[EMAIL PROTECTED]>, on 10/24/2005
at 09:28 AM, Nasuh KARAHALLI <[EMAIL PROTECTED]> said:
>the system give them a job the number say JOB22540 to JOB1 and let's
>say JOB22541 to JOB2 respectively.
I hope that you aren't relying on consecutive job numbers; that isn't
guarantied.
>JOB1 and JOB2 start in turn, but JOB2 first,
There is nothing in MVS that requires jobs to run in submission order.
There is something called DJC in JES3, but it isn't automatic: you
must supply control statements to define the sequencing restrictions.
There are exits and modifications to do something similar in JES2,
but, again, you must supply control statements to define the
sequencing restrictions.
If you don't have the Mellon mods or equivalent, you can alway let
JOB1 submit JOB2. If you have a job scheduler, you can define with the
proper sequencing restrictions and submit them through the scheduler.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
