Classification: Confidential
>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. > The simple solution to this is to not only have job 1 copy the file for job2, but also submit job2. Thus only only one job will be in the system an NODELAY will not be needed. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Paul Gilmartin Sent: Thursday, March 3, 2022 4:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2 DUPL_JOB parameter [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] On Thu, 3 Mar 2022 22:20:15 +0000, Frank Swarbrick wrote: >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. > Shouldn't SYSDSN ENQ resolve this? Or did job 1 carelessly write with DISP=SHR? (Were these Classic data sets or UNIX files?) Would DSENQSHR alleviate or aggravate the misbehavior? >That's why I want to be able detect this and make changes before going back to >NODELAY. > And you might need to deal with ambiguity in operator commands. And there's no guarantee that jobs will run in the order submitted. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ::DISCLAIMER:: ________________________________ The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ________________________________ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
