I tried this once for a single class in our dev region and it screwed up some jobs that depend on DELAY for sequencing. 🙁 Of course something could be done about that, but I didn't feel like dealing with it at the time. ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Charles Mills <[email protected]> Sent: Thursday, February 1, 2024 10:15 AM To: [email protected] <[email protected]> Subject: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas?
I am not a sysprog but I occasionally play one in my spare time. I am thinking of changing a system that I control to DUPL_JOB=NODELAY. Any gotchas? Anything I need to consider before I do this? Do most/many of you run with NO_DELAY? I am trying to solve a problem where I have jobs delayed because the names are duplicates. I can't easily change the jobnames. I can't think of any issues. We don't have any significant automation. I can't think of anything where jobs are referenced by name rather than Job ID. What should I be considering? Thanks, Charles ---------------------------------------------------------------------- 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
