Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Lizette Koehler]

I think that JES2 z/OS V2.2 is starting to include some basic job scheduling 
functions.

Configuring and activating job groups

There is a new JES2 initialization statement and command, GRPDEF, that controls 
job group processing. Keywords on GRPDEF control the number of data areas 
available for group processing and the number of jobs that can run 
concurrently. Data for job groups is stored in a data area called a ZJC. The 
number of data areas needed to represent a group is dictated by the complexity 
of the group. One data area is needed for the group, one for each job in the 
group, and one for each dependency. The 4 job group described earlier would 
require 1 ZJC for the group, 4 for jobs in the group, and 4 for each of the 
dependencies, for a total of 9 data areas.

The number of ZJCs (ZJCNUM=) is defaulted to 1000, allowing limited usage of 
the function. The value can be configured from 6 (only useful for basic 
testing) to 500,000.

The other configuration keyword on GRPDEF is the number of concurrent jobs that 
can be configured in a single job group. This is the CONCURRENT_MAX= keyword. 
By default, the limit is set to zero, disabling the function. To allow users to 
use concurrent execution, this needs to be configured to a higher value. Valid 
range is 0 to 200.

All the functions of job groups are only available when JES2 is in the z22 
$ACTIVATE mode. The current $ACTIVATE mode can be displayed using the $D 
ACTIVATE command. The command also list any reasons why you cannot activate to 
z22, if you are in z11 mode. There is also a health check that reports if you 
are not in z22 mode and what is needed to activate to z22 mode. In general, all 
members must be running z/OS 2.2 or later. SPOOLDEF CYL_MANAGED=ALLOWED must be 
set, and the checkpoint data sets have to be large enough to hold the larger 
data areas.

Doing a $ACTIVATE to z22 mode also enables a number of other functions in JES2 
2.2, such as increased limits for checkpoint data, dynamic changes to the 
checkpoint size, and a large cache for spool space allocations.

JES2 can be retroactivated to z11 mode by the $ACTIVATE command, but to do 
this, there can be no job groups defined in the system

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jesse 1 Robinson
> Sent: Friday, September 15, 2017 12:14 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Can you run multiple jobs with the same job name at the same
> time on JES2?
> 
> I do sympathize with shops that cannot afford a highfalutin job scheduling
> package. I've heard of fairly cheap alternatives although I have no
> recommendations. WLM should help with managing batch load.
> 
> The most promising new mechanism is the one (being) built into JES2 itself.
> It's designed to handle the serialization function--even fairly complex
> relationships--not just overall system load. You have to get current to
> implement it, but once there the price is attractive. ;-)
> 
> .
> .
> 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 [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Tom Marchant
> Sent: Friday, September 15, 2017 11:11 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: Can you run multiple jobs with the same job name at
> the same time on JES2?
> 
> On Fri, 15 Sep 2017 11:26:53 -0500, David G. Yeager wrote:
> 
> >If there is one thing I've learned from following these threads is
> >that every shop is different.   If we ran (could afford) Thru-Put
> >manager , we wouldn't rely on single threading same name jobs, but we
> >do it , not for order , so much as to limit "thruput", because we need
> >a poor man's solution being poor men.
> 
> Have you considered WLM managed Initiators?
> 
> --
> Tom Marchant
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Jesse 1 Robinson]

I do sympathize with shops that cannot afford a highfalutin job scheduling 
package. I've heard of fairly cheap alternatives although I have no 
recommendations. WLM should help with managing batch load.

The most promising new mechanism is the one (being) built into JES2 itself. 
It's designed to handle the serialization function--even fairly complex 
relationships--not just overall system load. You have to get current to 
implement it, but once there the price is attractive. ;-)

.
.
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 [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Friday, September 15, 2017 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Can you run multiple jobs with the same job name at the 
same time on JES2?

On Fri, 15 Sep 2017 11:26:53 -0500, David G. Yeager wrote:

>If there is one thing I've learned from following these threads is 
>that every shop is different.   If we ran (could afford) Thru-Put 
>manager , we wouldn't rely on single threading same name jobs, but we 
>do it , not for order , so much as to limit "thruput", because we need 
>a poor man's solution being poor men.

Have you considered WLM managed Initiators?

--
Tom Marchant


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Tom Marchant]

On Fri, 15 Sep 2017 11:26:53 -0500, David G. Yeager wrote:

>If there is one thing I've learned from following these threads is 
>that every shop is different.   If we ran (could afford) Thru-Put 
>manager , we wouldn't rely on single threading same name jobs, 
>but we do it , not for order , so much as to limit "thruput",  
>because we need a poor man's solution being poor men.

Have you considered WLM managed Initiators?

-- 
Tom Marchant

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[David G. Yeager]

If there is one thing I've learned from following these threads is that every 
shop is different.   If we ran (could afford) Thru-Put manager , we wouldn't 
rely on single threading same name jobs,  but we do it , not for order , so 
much as to limit "thruput",  because we need a poor man's solution being poor 
men.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Elardus Engelbrecht]

Jesse Robinson wrote:

>Depending on the one-jobname restriction was indeed a 'convenient' method of 
>serialization--but a method fraught with peril.

Yaaa, tell me. ;-)

 
>One-jobname was always a poor man's solution to a complex problem. With even a 
>modestly sophisticated job scheduling system, serialization was achieved far 
>more capably.   

Very true. Use Automation Software to schedule jobs based on Return Code (from 
SYSLOG or from jobs themselves) and success/failure of previous jobs ran on 
same or other LPARs. Use the Automation Software handling of 'incoming' and 
'outgoing' condition codes.
 
With this setup there is not a problem with same or different jobnames and the 
order in which they are running.

One example: every day we run SMF Dump, Automation Software collects the 
results of those SMF jobs and pass it on as conditions to release other jobs 
which post process SMF data. The jobnames can be the same or not, it does not 
matter.

Before we got Automation Software, it was a real PITA to ensure jobs with the 
same names ran in the right sequence. The Operators sometimes released the 
wrong job, surely all h*ll broke loose when the angry client had to restore 
their data.

Groete / Greetings
Elardus Engelbrecht

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Ed Jaffe]

On 9/14/2017 9:53 AM, Paul Gilmartin wrote:

On Thu, 14 Sep 2017 11:17:38 -0500, Steve Beaver wrote:


You're talking it's about a change that is possible but it would be such a 
shock to people from what they know he's probably going to get fired for that 
one


I wonder if Ed Jaffe knows of anyone who got fired?


Haha! None that I know of...

[snip]


I wonder how all this plays with the SUBMIT command and 8-character TSO IDs?


With 8-character userids,  no character is appended the the userid when 
submitting JCL without a proper job card. Therefore, all such jobs will 
run with the same job name whereas previously they might have all been 
different.


Of course, that's not a problem for those of us already using 
DUPL_JOB=NODELAY (JES2) or DUPJOBNM=YES (JES3) which we have done for 
over eleven years. ;-)


--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Jesse 1 Robinson]

Depending on the one-jobname restriction was indeed a 'convenient' method of 
serialization--but a method fraught with peril. Along with the one-jobname 
restriction a shop would also need to run with only one internal reader because 
if more than one, it's unpredictable which of two like-named jobs would get 
initiated first. So one at a time, yes, but out of order. Otherwise the whole 
system was hampered by a single threaded entry for all jobs regardless of name. 
 

One-jobname was always a poor man's solution to a complex problem. With even a 
modestly sophisticated job scheduling system, serialization was achieved far 
more capably.  

.
.
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 [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Thursday, September 14, 2017 9:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Can you run multiple jobs with the same job name at the 
same time on JES2?

On Thu, 14 Sep 2017 11:17:38 -0500, Steve Beaver wrote:

>You're talking it's about a change that is possible but it would be 
>such a shock to people from what they know he's probably going to get 
>fired for that one
> 
I wonder if Ed Jaffe knows of anyone who got fired?

It feels as if Steve is rationalizing a MISCONCEPTION.

I wonder how an ISV's removing the restriction (or not doing so) plays with 
customer emulation testing?  (New options exponentially increase the burden of 
such testing.)

I wonder how all this plays with the SUBMIT command and 8-character TSO IDs?

>> -Original Message-
>> From: Steve Beaver
>> Sent: Thursday, September 14, 2017 10:23 AM
>> 
>> The SYSTEM will NEVER allow you to run 2 or more batch jobs with the same 
>> name.  That lock/prohibition has been There since JES was written.  It been 
>> a convenient way to single thread multiple jobs with the same name.

-- gil


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Paul Gilmartin]

On Thu, 14 Sep 2017 11:17:38 -0500, Steve Beaver wrote:

>You're talking it's about a change that is possible but it would be such a 
>shock to people from what they know he's probably going to get fired for that 
>one
> 
I wonder if Ed Jaffe knows of anyone who got fired?

It feels as if Steve is rationalizing a MISCONCEPTION.

I wonder how an ISV's removing the restriction (or not doing so) plays with
customer emulation testing?  (New options exponentially increase the burden
of such testing.)

I wonder how all this plays with the SUBMIT command and 8-character TSO IDs?

>> -Original Message-
>> From: Steve Beaver
>> Sent: Thursday, September 14, 2017 10:23 AM
>> 
>> The SYSTEM will NEVER allow you to run 2 or more batch jobs with the same 
>> name.  That lock/prohibition has been There since JES was written.  It been 
>> a convenient way to single thread multiple jobs with the same name.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Allan Staller]

Steve,
I took your prior comment to mean it *IS NOT* possible, period.

IBM has supported allowing duplicate batch jobs to run for many years now.
I did not say you should. I did say you could.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Steve Beaver
Sent: Thursday, September 14, 2017 11:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can you run multiple jobs with the same job name at the same time 
on JES2?

You're talking it's about a change that is possible but it would be such a 
shock to people from what they know he's probably going to get fired for that 
one

Sent from my iPhone

Sorry for any grammar problems 

> On Sep 14, 2017, at 11:11, Allan Staller  wrote:
> 
> That is no longer true. There is an option to run duplicate batch as of z/OS 
> 2.1(?). 
> Might be earlier.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Steve Beaver
> Sent: Thursday, September 14, 2017 10:23 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Can you run multiple jobs with the same job name at the same 
> time on JES2?
> 
> The SYSTEM will NEVER allow you to run 2 or more batch jobs with the same 
> name.  That lock/prohibition has been There since JES was written.  It been a 
> convenient way to single thread multiple jobs with the same name.
> 
> That being said you can have MULTIPLE STC's with the same name but you 
> best be very, very careful
> 
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Lizette Koehler
> Sent: Thursday, September 14, 2017 8:50 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Can you run multiple jobs with the same job name at the same 
> time on JES2?
> 
> There is. It is documented in the JES2 INIT and TUNING.   Go to www.ibm.com 
> and search on JES2 DUPLICATE JOBS
> 
> 
> 
> However, what problem are you trying to solve?
> 
> When you switch this on - it will be an way of running that JES2 supports but 
> it is not normal for JES2.  It was setup with serial processing.
> 
> If you run duplicate job names, you will probably hit resource contention.  
> Everyone wanting the same dataset, for example.
> 
> If you specify DUPL_JOB=NODELAY, jobs with the same job name may run 
> concurrently with adverse effects. Make certain that this serialization 
> mechanism is not being used in your environment before changing this 
> parameter.
> 
> 
> Lizette
> 
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
>> On Behalf Of Mark Regan
>> Sent: Thursday, September 14, 2017 6:29 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Can you run multiple jobs with the same job name at the same 
>> time on JES2?
>> 
>> Just asking if there is a way.
>> 
>> --
>> 
>> Regards,
>> 
>> Mark T. Regan
>> 
> 
> --
> 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
> 
> 
> ::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

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Steve Beaver]

You're talking it's about a change that is possible but it would be such a 
shock to people from what they know he's probably going to get fired for that 
one

Sent from my iPhone

Sorry for any grammar problems 

> On Sep 14, 2017, at 11:11, Allan Staller  wrote:
> 
> That is no longer true. There is an option to run duplicate batch as of z/OS 
> 2.1(?). 
> Might be earlier.
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Steve Beaver
> Sent: Thursday, September 14, 2017 10:23 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Can you run multiple jobs with the same job name at the same 
> time on JES2?
> 
> The SYSTEM will NEVER allow you to run 2 or more batch jobs with the same 
> name.  That lock/prohibition has been There since JES was written.  It been a 
> convenient way to single thread multiple jobs with the same name.
> 
> That being said you can have MULTIPLE STC's with the same name but you best 
> be very, very careful  
> 
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Lizette Koehler
> Sent: Thursday, September 14, 2017 8:50 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Can you run multiple jobs with the same job name at the same 
> time on JES2?
> 
> There is. It is documented in the JES2 INIT and TUNING.   Go to www.ibm.com 
> and search on JES2 DUPLICATE JOBS
> 
> 
> 
> However, what problem are you trying to solve?
> 
> When you switch this on - it will be an way of running that JES2 supports but 
> it is not normal for JES2.  It was setup with serial processing.
> 
> If you run duplicate job names, you will probably hit resource contention.  
> Everyone wanting the same dataset, for example.
> 
> If you specify DUPL_JOB=NODELAY, jobs with the same job name may run 
> concurrently with adverse effects. Make certain that this serialization 
> mechanism is not being used in your environment before changing this 
> parameter.
> 
> 
> Lizette
> 
>> -Original Message-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
>> On Behalf Of Mark Regan
>> Sent: Thursday, September 14, 2017 6:29 AM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Can you run multiple jobs with the same job name at the same 
>> time on JES2?
>> 
>> Just asking if there is a way.
>> 
>> --
>> 
>> Regards,
>> 
>> Mark T. Regan
>> 
> 
> --
> 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
> 
> 
> ::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

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Allan Staller]

That is no longer true. There is an option to run duplicate batch as of z/OS 
2.1(?). 
Might be earlier.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Steve Beaver
Sent: Thursday, September 14, 2017 10:23 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can you run multiple jobs with the same job name at the same time 
on JES2?

The SYSTEM will NEVER allow you to run 2 or more batch jobs with the same name. 
 That lock/prohibition has been There since JES was written.  It been a 
convenient way to single thread multiple jobs with the same name.

That being said you can have MULTIPLE STC's with the same name but you best be 
very, very careful  



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Thursday, September 14, 2017 8:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can you run multiple jobs with the same job name at the same time 
on JES2?

There is. It is documented in the JES2 INIT and TUNING.   Go to www.ibm.com and 
search on JES2 DUPLICATE JOBS



However, what problem are you trying to solve?

When you switch this on - it will be an way of running that JES2 supports but 
it is not normal for JES2.  It was setup with serial processing.

If you run duplicate job names, you will probably hit resource contention.  
Everyone wanting the same dataset, for example.

If you specify DUPL_JOB=NODELAY, jobs with the same job name may run 
concurrently with adverse effects. Make certain that this serialization 
mechanism is not being used in your environment before changing this parameter.


Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Mark Regan
> Sent: Thursday, September 14, 2017 6:29 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Can you run multiple jobs with the same job name at the same 
> time on JES2?
> 
> Just asking if there is a way.
> 
> --
> 
> Regards,
> 
> Mark T. Regan
> 

--
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


::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

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Ed Jaffe]

On 9/14/2017 8:22 AM, Steve Beaver wrote:

The SYSTEM will NEVER allow you to run 2 or more batch jobs with the same name. 
 That lock/prohibition has been
There since JES was written.  It been a convenient way to single thread 
multiple jobs with the same name.


That restriction was lifted over a decade ago and, like many others, we 
removed it immediately!


It was never a truly reliable way to single thread jobs because you 
could never fully depend on the processing order.


--
Phoenix Software International
Edward E. Jaffe
Chief Technology Officer
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Steve Beaver]

The SYSTEM will NEVER allow you to run 2 or more batch jobs with the same name. 
 That lock/prohibition has been
There since JES was written.  It been a convenient way to single thread 
multiple jobs with the same name.

That being said you can have MULTIPLE STC's with the same name but you best be 
very, very careful  



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Thursday, September 14, 2017 8:50 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Can you run multiple jobs with the same job name at the same time 
on JES2?

There is. It is documented in the JES2 INIT and TUNING.   Go to www.ibm.com and 
search on JES2 DUPLICATE JOBS



However, what problem are you trying to solve?

When you switch this on - it will be an way of running that JES2 supports but 
it is not normal for JES2.  It was setup with serial processing.

If you run duplicate job names, you will probably hit resource contention.  
Everyone wanting the same dataset, for example.

If you specify DUPL_JOB=NODELAY, jobs with the same job name may run 
concurrently with adverse effects. Make certain that this serialization 
mechanism is not being used in your environment before changing this parameter.


Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
> On Behalf Of Mark Regan
> Sent: Thursday, September 14, 2017 6:29 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Can you run multiple jobs with the same job name at the same 
> time on JES2?
> 
> Just asking if there is a way.
> 
> --
> 
> Regards,
> 
> Mark T. Regan
> 

--
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: Can you run multiple jobs with the same job name at the same time on JES2?

[Mark Regan]

In our case, we use Connect:Direct between LPARs and one of the functions
people use is the RUN TASK to tell CA7 to release a job on the receiving
end. Since they are calling the same job name (CDC7NDMT) that is run to
tell CA7 this, along with the job details, if there a whole bunch of
transfers taking place, all wanting to run that same job name (CDC7NDMT)
the release of the final processing job can get held up.

On Thu, Sep 14, 2017 at 9:50 AM Lizette Koehler 
wrote:

> There is. It is documented in the JES2 INIT and TUNING.   Go to
> www.ibm.com and search on JES2 DUPLICATE JOBS
>
>
>
> However, what problem are you trying to solve?
>
> When you switch this on - it will be an way of running that JES2 supports
> but it is not normal for JES2.  It was setup with serial processing.
>
> If you run duplicate job names, you will probably hit resource
> contention.  Everyone wanting the same dataset, for example.
>
> If you specify DUPL_JOB=NODELAY, jobs with the same job name may run
> concurrently with adverse effects. Make certain that this serialization
> mechanism is not being used in your environment before changing this
> parameter.
>
>
> Lizette
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of Mark Regan
> > Sent: Thursday, September 14, 2017 6:29 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: Can you run multiple jobs with the same job name at the same
> time on
> > JES2?
> >
> > Just asking if there is a way.
> >
> > --
> >
> > Regards,
> >
> > Mark T. Regan
> >
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
-- 

Regards,

Mark T. Regan

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Lizette Koehler]

There is. It is documented in the JES2 INIT and TUNING.   Go to www.ibm.com and 
search on JES2 DUPLICATE JOBS



However, what problem are you trying to solve?

When you switch this on - it will be an way of running that JES2 supports but 
it is not normal for JES2.  It was setup with serial processing.

If you run duplicate job names, you will probably hit resource contention.  
Everyone wanting the same dataset, for example.

If you specify DUPL_JOB=NODELAY, jobs with the same job name may run 
concurrently with adverse effects. Make certain that this serialization 
mechanism is not being used in your environment before changing this parameter.


Lizette

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Mark Regan
> Sent: Thursday, September 14, 2017 6:29 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Can you run multiple jobs with the same job name at the same time on
> JES2?
> 
> Just asking if there is a way.
> 
> --
> 
> Regards,
> 
> Mark T. Regan
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Can you run multiple jobs with the same job name at the same time on JES2?

[Steve Smith]

There is.

sas

On Thu, Sep 14, 2017 at 9:28 AM, Mark Regan  wrote:
> Just asking if there is a way.
>
> --
>
> Regards,
>
> Mark T. Regan
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
sas

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Can you run multiple jobs with the same job name at the same time on JES2?

[Mark Regan]

Just asking if there is a way.

-- 

Regards,

Mark T. Regan

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN