1. While I've never found it to be a huge issue, it seems like it's easy enough for two developers to submit jobs using the same name. Of course the way people generally ger around this is to use their user ID as part of the name, but then you are limited to only a few characters to make one job different from another. 2. 3. Or using a scheduler so you only submit the "next" job after the "previous" one has completed...
________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Steve Smith <[email protected]> Sent: Thursday, March 3, 2022 8:03 PM To: [email protected] <[email protected]> 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 [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
