Thomas Berg wrote:
BBB should of course have some "anti-parallel" mechanism, whether it be the same jobname or if that don't work, using dsn enq's for serializing.
As Bob Rutledge aptly pointed out, duplicate job names is no guarantee either.
I do believe that the data set ENQ/DEQ contention mechanism is strictly FIFO, so it should work to do what you've suggested. But, keep in mind that BBB will also (presumably) submit CCC, which will submit DDD and so forth.
If these jobs run for any significant amount of time at all, what you'll end up with is every initiator tied up running jobs that are "stuck" on an ENQ. And when one of these jobs abends, all of its "successor" jobs will have already been submitted, will run, and probably fail miserably.
The best approach (IMHO) for JES2 users is to have the last step of each job submit the next job.
-- Edward E Jaffe Phoenix Software International, Inc 5200 W Century Blvd, Suite 800 Los Angeles, CA 90045 310-338-0400 x318 [email protected] http://www.phoenixsoftware.com/ ---------------------------------------------------------------------- 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
