Re: Running same stc in a LPAR
On Sun, 22 Nov 2020, at 04:08, Peter wrote: > Is it possible for JES to allow to run two started task with the same name > in a LPAR(not sysplex). Twenty+ years ago there wasn't a problem running multiple STCs with the same name, if you could make sure there'd be no dataset contention. I remember using automation to start some STCs with a parameter that was used as one qualifier in every temporary datasetname that that STC would allocate. I think (but can't remember how) that the automation that started the STCs made sure that different values were used for that qualifier. So eg in the STC JCL there might have been //SYSUT2 DD DISP=(NEW,DELETE,DELETE),SPACE=(TRK,(5,5)) // UNIT=SYSDA,DSN=APP3.STC#TEMP. //SYSUT3 DD DISP=(NEW,DELETE,DELETE),SPACE=(TRK,(5,5)) // UNIT=SYSDA,DSN=APP3.STC#TEMP. and that instance of the STC was started with a unique T= parm. -- Jeremy Nicoll - my opinions are my own. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running same stc in a LPAR
And for programs that do not prohibit duplicates themselves, I remember writing a short program that I would include as the top step in an STC that checked for a duplicate address space name, and would spit out a message and abend if it found another already running. On 11/23/2020 10:44 AM, Jesse 1 Robinson wrote: An example of duplicate STCs is 'INIT'. No action is required to run an unlimited number of initiators. As someone else pointed out, a particular STC may and often does prohibit duplicates in its own code, but that is not an MVS limitation. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Wasik Sent: Monday, November 23, 2020 7:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Running same stc in a LPAR *** EXTERNAL EMAIL - Use caution when opening links or attachments *** You can allow duplicate jobs to run based on JOBCLASS (DUPL_JOB=DELAY|NODELAY as of z/OS 1.7 - 2005), at a system level (JOBDEF DUPL_JOB=DELAY|NODELAY as of OS/390 release 3 - 1997) and with z/OS 2.4, you can exempt a particular job from duplicate job delays using the JES2 POLICY function. Tom Wasik -- 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: Running same stc in a LPAR
An example of duplicate STCs is 'INIT'. No action is required to run an unlimited number of initiators. As someone else pointed out, a particular STC may and often does prohibit duplicates in its own code, but that is not an MVS limitation. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of Tom Wasik Sent: Monday, November 23, 2020 7:50 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Running same stc in a LPAR *** EXTERNAL EMAIL - Use caution when opening links or attachments *** You can allow duplicate jobs to run based on JOBCLASS (DUPL_JOB=DELAY|NODELAY as of z/OS 1.7 - 2005), at a system level (JOBDEF DUPL_JOB=DELAY|NODELAY as of OS/390 release 3 - 1997) and with z/OS 2.4, you can exempt a particular job from duplicate job delays using the JES2 POLICY function. Tom Wasik -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running same stc in a LPAR
You can allow duplicate jobs to run based on JOBCLASS (DUPL_JOB=DELAY|NODELAY as of z/OS 1.7 - 2005), at a system level (JOBDEF DUPL_JOB=DELAY|NODELAY as of OS/390 release 3 - 1997) and with z/OS 2.4, you can exempt a particular job from duplicate job delays using the JES2 POLICY function. Tom Wasik -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running same stc in a LPAR
It is not the default; it has to be enabled by job class. When I first used it in c. 2009, I recall finding that it was really very recent at the time; so I would agree with that: it is relatively recent, even today. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of Peter Relson Sent: Sunday, November 22, 2020 8:03 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Running same stc in a LPAR [External Email. Exercise caution when clicking links or opening attachments.] You can also run duplicate batch jobs at the same time if you just feel like it; I have twenty running right now, with a thousand more sitting in the input queue. This is a relatively recent enhancement to the operating system. I don't recall if allowing this is default behavior or needs to be enabled. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running same stc in a LPAR
true: jes parm dupl_job=nodelay, but the op asked about STCs. ITschak *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* On Sun, Nov 22, 2020 at 3:03 PM Peter Relson wrote: > > You can also run duplicate batch jobs at the same time if you just feel > like it; I have twenty running right now, with a thousand more sitting in > the input queue. > > > This is a relatively recent enhancement to the operating system. > I don't recall if allowing this is default behavior or needs to be > enabled. > > Peter Relson > z/OS Core Technology Design > > > -- > 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: Running same stc in a LPAR
You can also run duplicate batch jobs at the same time if you just feel like it; I have twenty running right now, with a thousand more sitting in the input queue. This is a relatively recent enhancement to the operating system. I don't recall if allowing this is default behavior or needs to be enabled. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running same stc in a LPAR
STCs can be started with a unique name (S xxx.yyy where yyy make it unique). However, the TSC itself can block coincarency by enquing a resource exclusively. so the answer is yes, but depends on the STC. ITschak *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere Platform* *|* *Information Security Continuous Monitoring for Z/OS, zLinux and IBM I **| * *|* *Email**: i_mugz...@securiteam.co.il **|* *Mob**: +972 522 986404 **|* *Skype**: ItschakMugzach **|* *Web**: www.Securiteam.co.il **|* On Sun, Nov 22, 2020 at 1:45 PM Binyamin Dissen wrote: > On Sun, 22 Nov 2020 08:08:52 +0400 Peter wrote: > > :>Is it possible for JES to allow to run two started task with the same > name > :>in a LPAR(not sysplex). > > Happens all the time. > > :>One of a started task in our lpar is running two stc with same name but > :>second one notifies that this particular task is already active. > > As you can see, it started and then decided to end because of the > duplicate. > JES had nothing to do with it. > > :>Is it a JES functionality to allow a task to run with same name or the > :>product which has the capability of running in duplicate as many times > even > :>though it is initialised in one STC alone ? > > Yes. > > -- > Binyamin Dissen > http://www.dissensoftware.com > > Director, Dissen Software, Bar & Grill - Israel > > > Should you use the mailblocks package and expect a response from me, > you should preauthorize the dissensoftware.com domain. > > I very rarely bother responding to challenge/response systems, > especially those from irresponsible companies. > > -- > 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: Running same stc in a LPAR
On Sun, 22 Nov 2020 08:08:52 +0400 Peter wrote: :>Is it possible for JES to allow to run two started task with the same name :>in a LPAR(not sysplex). Happens all the time. :>One of a started task in our lpar is running two stc with same name but :>second one notifies that this particular task is already active. As you can see, it started and then decided to end because of the duplicate. JES had nothing to do with it. :>Is it a JES functionality to allow a task to run with same name or the :>product which has the capability of running in duplicate as many times even :>though it is initialised in one STC alone ? Yes. -- Binyamin Dissen http://www.dissensoftware.com Director, Dissen Software, Bar & Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running same stc in a LPAR
You see it more often than you think. Go do a 'd j,bpxas' or a 'd j,init', as examples. It's common and helpful for others to have duplicates, like your HSM product, for instance (not commonly DFSMShsm). You can also run duplicate batch jobs at the same time if you just feel like it; I have twenty running right now, with a thousand more sitting in the input queue. First Horizon Bank Mainframe Technical Support -Original Message- From: IBM Mainframe Discussion List On Behalf Of David Spiegel Sent: Saturday, November 21, 2020 11:27 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Running same stc in a LPAR [External Email. Exercise caution when clicking links or opening attachments.] Hi Peter, I've seen this, but, not recently. Regards, David On 2020-11-21 23:08, Peter wrote: > Hello > > Is it possible for JES to allow to run two started task with the same > name in a LPAR(not sysplex). > > One of a started task in our lpar is running two stc with same name > but second one notifies that this particular task is already active. > > Is it a JES functionality to allow a task to run with same name or the > product which has the capability of running in duplicate as many times > even though it is initialised in one STC alone ? > > Could someone please shed your light on above ? > > > Peter > > -- > 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 Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Running same stc in a LPAR
Hi Peter, I've seen this, but, not recently. Regards, David On 2020-11-21 23:08, Peter wrote: Hello Is it possible for JES to allow to run two started task with the same name in a LPAR(not sysplex). One of a started task in our lpar is running two stc with same name but second one notifies that this particular task is already active. Is it a JES functionality to allow a task to run with same name or the product which has the capability of running in duplicate as many times even though it is initialised in one STC alone ? Could someone please shed your light on above ? Peter -- 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: Running same stc in a LPAR
You can the same started name more than once on any lpar. Now the product itself may not allow it based on enqueues and other things, that is why you most likely got the notification that the product was already active. For our automation product we use CA OPS/MVS and he runs multiple of the same started task name on the same lpar. JES2 has nothing to do with this. Michael From: IBM Mainframe Discussion List on behalf of Peter Sent: Saturday, November 21, 2020 10:08 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Running same stc in a LPAR [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.] Hello Is it possible for JES to allow to run two started task with the same name in a LPAR(not sysplex). One of a started task in our lpar is running two stc with same name but second one notifies that this particular task is already active. Is it a JES functionality to allow a task to run with same name or the product which has the capability of running in duplicate as many times even though it is initialised in one STC alone ? Could someone please shed your light on above ? Peter -- 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
Running same stc in a LPAR
Hello Is it possible for JES to allow to run two started task with the same name in a LPAR(not sysplex). One of a started task in our lpar is running two stc with same name but second one notifies that this particular task is already active. Is it a JES functionality to allow a task to run with same name or the product which has the capability of running in duplicate as many times even though it is initialised in one STC alone ? Could someone please shed your light on above ? Peter -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
