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
@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
: (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
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
-
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
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
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
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* *|*
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
: 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 sam
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
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
12 matches
Mail list logo
