Classification: Confidential JES2 (for several years now) has offered the option of allowing duplicate names to run concurrently.
-----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Charles Mills Sent: Thursday, March 3, 2022 4:08 PM To: [email protected] 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.] Certainly everything you need to know is in SMF 30. You can tell when a Job arrives in JES, when it gets initiated, and when it finishes. It would be an interesting programming exercise to model z/OS behavior and compute duplicate job delay. It seems to me -- with the caveat that I am not an expert in JES2 job selection -- that it might not be black and white? Couldn't a job come into the system and be held as a duplicate. Then the other job finishes but now there is no initiator of the right class. And then an initiator frees up but now there is a new duplicate running. So ... how much of that delay is due to duplicate jobnames? (Or as I say, perhaps I do not know how job selection works.) SMF30HQT 4 binary Time following job preparation when the job was ineligible for execution for reasons not included in SMF30RQT. This includes job hold, job class hold, job queue hold, duplicate jobname serialization, and job class execution limits. If the JOB statement specified TYPRUN=HOLD, the time that the job is held for this reason is not included. The time is in 1024-microsecond units. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Frank Swarbrick Sent: Thursday, March 3, 2022 11:18 AM To: [email protected] Subject: JES2 DUPL_JOB parameter 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. ---------------------------------------------------------------------- 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 ::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 [email protected] with the message: INFO IBM-MAIN
