Re: EXTERNAL EMAIL: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas?
And poorly designed applications that dynamically request the same resources exclusively, but in a different order in various separate instances. Michael At 01:46 PM 2/1/2024, Seymour J Metz wrote: Content-Transfer-Encoding: base64You only get that deadly embrace with dynamic allocation. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ×¢Ö·× ×ִשְ×רָ×Öµ× ×Ö·× × ÖµÖ£×¦Ö·× ×ִשְ×רָ×ÖµÖ× ×Ö¹Ö¥× ×ְשַ×קֵּÖר From: IBM Mainframe Discussion List To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: EXTERNAL EMAIL: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchasYÙÙ\Ý\ÜÝYHÛH^H\ÜXÝ]H\Èif all these jobs are on Initiators (rather than delayed in the input queue) how much are they count to block each other with dataset contention etc. Theres a possibility for some to even get into deadly embraces where 2 jobs lock each other out and can never finish because each is holding resources that the other needs. Nowadays with scheduling packages and other advancements this is not common but in the past it was frequent. We run with Delay so jobs of the same name (normally doing the same thing) Queue . Jerry Whitteridge Sr Manager Managed Services jerry.whitteri...@albertsons.com 480 578 7889 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, February 1, 2024 10:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: EXTERNAL EMAIL: 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EXTERNAL EMAIL: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas?
You only get that deadly embrace with dynamic allocation. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר From: IBM Mainframe Discussion List on behalf of Jerry Whitteridge Sent: Thursday, February 1, 2024 12:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: EXTERNAL EMAIL: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas? Biggest issue from my perspective is if all these jobs are on Initiators (rather than delayed in the input queue) how much are they count to block each other with dataset contention etc. Theres a possibility for some to even get into deadly embraces where 2 jobs lock each other out and can never finish because each is holding resources that the other needs. Nowadays with scheduling packages and other advancements this is not common but in the past it was frequent. We run with Delay so jobs of the same name (normally doing the same thing) Queue . Jerry Whitteridge Sr Manager Managed Services jerry.whitteri...@albertsons.com 480 578 7889 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, February 1, 2024 10:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: EXTERNAL EMAIL: 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: EXTERNAL EMAIL: JES2 JOBDEF DUPL_JOB=NODELAY - Any gotchas?
Biggest issue from my perspective is if all these jobs are on Initiators (rather than delayed in the input queue) how much are they count to block each other with dataset contention etc. Theres a possibility for some to even get into deadly embraces where 2 jobs lock each other out and can never finish because each is holding resources that the other needs. Nowadays with scheduling packages and other advancements this is not common but in the past it was frequent. We run with Delay so jobs of the same name (normally doing the same thing) Queue . Jerry Whitteridge Sr Manager Managed Services jerry.whitteri...@albertsons.com 480 578 7889 -Original Message- From: IBM Mainframe Discussion List On Behalf Of Charles Mills Sent: Thursday, February 1, 2024 10:15 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: EXTERNAL EMAIL: 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN Warning: All e-mail sent to this address will be received by the corporate e-mail system, and is subject to archival and review by someone other than the recipient. This e-mail may contain proprietary information and is intended only for the use of the intended recipient(s). If the reader of this message is not the intended recipient(s), you are notified that you have received this message in error and that any review, dissemination, distribution or copying of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
