Doing this regularly, my biggest problem is that a set of jobs running ISPF in batch, all with //ISPPROF set to a temporary dataset fall over, because it's in use. Adding a second or so delay between submitting them solves the issue, most of the time.
On Thu, 1 Feb 2024, 19:15 Charles Mills, <[email protected]> wrote: > 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
