That's an alternative; it's not the only one. JES3 has had DJC since before it was JES3, and JES2 now has SCHEDULE statement.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Steve Smith [sasd...@gmail.com] Sent: Thursday, March 3, 2022 10:03 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2 DUPL_JOB parameter I wonder what the urgency is to run duplicate job names simultaneously. Jobnames are cheap enough, so why not give them different names if you want them run together. Using the jobname to single-thread a slew of repetitive jobs is not that uncommon, and perfectly reasonable as long as you aren't depending on the order they run. In many of those scenarios, the alternative would be lots of initiators jammed up with jobs waiting on DSN enqueues. sas ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
