I know for a fact that we have some jobs that depend on DELAY, because I turned on NODELAY and it caused an issue. Two jobs with the same name are submitted at the same time (or one after the other), where job 1 copies a file to a second file, and job 2 copies the second file to a third file. With NODELAY they ran "at the same time" so the copy from file 2 to file 3 failed because the copy from 1 to 2 was still running.
That's why I want to be able detect this and make changes before going back to NODELAY. ________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Radoslaw Skorupka <[email protected]> Sent: Thursday, March 3, 2022 2:53 PM To: [email protected] <[email protected]> Subject: Re: JES2 DUPL_JOB parameter W dniu 03.03.2022 o 20:17, Frank Swarbrick pisze: > I've long (ever since we started our migration from VSE to z/OS in 2008) > disliked the default of DUPL_JOB=DELAY, but I was overridden in setting > NODELAY because of the "it's always been this way" attitude, and lack of > desire to determine if there were any dependencies on the behavior. > > I am curious (but not hopeful) if there is anything available to log or > otherwise note when a job is delayed because it has the same name as a job > that is already running. Specifically, I am looking to find processes that > depend on the DELAY behavior. I think System Automation could note such event, however if you don't want this setting then why do you keep it effective? -- Radoslaw Skorupka Lodz, Poland ---------------------------------------------------------------------- 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
