On Wed, 11 Feb 2009 14:31:43 -0500, Veilleux, Jon L
wrote:
>I kind of missed some of the posts for this, but if you really want them
>to run one by one, you could give them their own job class and only
>define one initiator for that class.
Covered in earlier messages, Jon.
That would ensure the
tney Bowes Business Insight
http://centrus.com
W: (720) 564-3056
C: (303) 818-8222
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf
Of Walt Farrell
Sent: Wednesday, February 11, 2009 12:21
To: IBM-MAIN@bama.ua.edu
Subject: Re: JCL job execution
List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Walt Farrell
Sent: Wednesday, February 11, 2009 2:21 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: JCL job execution order
On Wed, 11 Feb 2009 11:13:07 -0700, David Logan
wrote:
> You can prevent
>temporary dataset name conflicts by ensuring that th
If You have any more sofisticated requirements,
You have to create Your own little job scheduler.
That occupies of course an extra initiator during the
execution of all application jobs.
(Using such one myself.)
Regards,
Thomas Berg
__
Thomas Berg Spe
nframe Discussion List
> [mailto:ibm-m...@bama.ua.edu] För Edward Jaffe
> Skickat: den 11 februari 2009 20:07
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: SV: SV: SV: JCL job execution order
>
> Thomas Berg wrote:
> > 2. At most there will 2 jobs occupying the initiators, 1 th
On Wed, 11 Feb 2009 11:13:07 -0700, David Logan wrote:
> You can prevent
>temporary dataset name conflicts by ensuring that the last step that uses a
>temporary uses DISP=(OLD,DELETE)
>
You're right that the user can certainly prevent the conflicts by making
sure his JCL always has a DISP=(OLD,D
Thomas Berg wrote:
2. At most there will 2 jobs occupying the initiators, 1 thats
executing and 1 thats wating for dataset.
(AAA resp BBB, then BBB resp CCC, and so on.)
And, if AAA abends, BBB will run anyway and submit CCC, which will
submit DDD, and so on. Doesn't sound right to me. But,
> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List
> [mailto:ibm-m...@bama.ua.edu] För Edward Jaffe
> Skickat: den 11 februari 2009 16:41
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: SV: SV: JCL job execution order
>
> Thomas Berg wrote:
> >
, Pitney Bowes Business Insight
http://centrus.com
W: (720) 564-3056
C: (303) 818-8222
-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf
Of Walt Farrell
Sent: Wednesday, February 11, 2009 08:57
To: IBM-MAIN@bama.ua.edu
Subject: Re: JCL job
On Wed, 11 Feb 2009 08:05:18 -0800, Edward Jaffe wrote:
>
>The job cards and JECL are shown below. Note the '/*ROUTE XEQ' JES2 JECL
>card. That's to be sure the jobs are sent to a JES3 node--in case
>they're accidentally submitted under JES2.
>
Snip!
Very interesting. Thanks, Ed!
--
Tom Marchan
On Wed, 11 Feb 2009 09:57:19 -0600, Walt Farrell wrote:
>
>If an automated process is doing the submission, why couldn't it build a
>nested job stream. It would read the first job, and add a step to submit
>the second. While building the SYSIN file containing the 2nd job, it could
>add a step to
On Tue, 10 Feb 2009 23:49:16 -0500, Robert A. Rosenberg wrote:
>
>The simplest method (as others have stated) is to have each job
>submit the next (with the last step being a COND=EVEN submission via
>INTRDR). You can also place it as the first step IF you have an
>IEFBR14 last step with a DD DSN=U
Vernooy, C.P. - SPLXM wrote:
It is FIFO in the order that the jobs start to execute, but there still
is no guarantee to control this, so this stil does not solve the
problem.
His suggestion was to have each job start the next one as its first
step. So, the order of ENQ is guaranteed.
--
E
Dave Salt wrote:
I'm starting to think that maybe I can allow the existing process to generate
the JCL, but my process would pass it a switch that tells it not to submit the
job. A fraction of a second later my process would call the existing process to
generate the next job, and the switch wo
On Wed, 11 Feb 2009 09:39:48 -0500, Dave Salt wrote:
>The only messy part might be ensuring the step names are unique throughout
the job, but other than that I think this might be the best solution?
And that temporary dsnames don't conflict (e.g., DSN=&TEMP with
DISP=(NEW,PASS)), and that you don
lt
> Sent: Wednesday, February 11, 2009 07:40
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: JCL job execution order
>
> > From: jch...@ussco.com
> > That's my reading as well: Job AAA must complete (successfully or
not)
> > before Job BBB begins execution; Job BBB mu
"Edward Jaffe" wrote in message
news:<4992f17b.5010...@phoenixsoftware.com>...
> Thomas Berg wrote:
> > BBB should of course have some "anti-parallel"
> > mechanism, whether it be the same jobname or
> > if that don't work, using dsn enq's for
> > serializing.
> >
>
> As Bob Rutledge aptl
Thomas Berg wrote:
BBB should of course have some "anti-parallel"
mechanism, whether it be the same jobname or
if that don't work, using dsn enq's for
serializing.
As Bob Rutledge aptly pointed out, duplicate job names is no guarantee
either.
I do believe that the data set ENQ/DEQ conte
Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf
Of Dave Salt
Sent: Wednesday, February 11, 2009 07:40
To: IBM-MAIN@bama.ua.edu
Subject: Re: JCL job execution order
> From: jch...@ussco.com
> That's my reading as well: Job AAA must complete (successfully or not)
> before
> From: jch...@ussco.com
> That's my reading as well: Job AAA must complete (successfully or not)
> before Job BBB begins execution; Job BBB must complete (successfully or
> not) before Job CCC begins execution, and so on. I.e., it doesn't
> matter whether none, some or all of the jobs complete suc
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Edward Jaffe
>
> Thomas Berg wrote:
> > Others have suggested that AAA ends with submitting BBB, etc.
> > But:
> > - If AAA abends before the submit step, should BBB be
> > submitted in that case also ?
> > - Sometimes
Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List
> [mailto:ibm-m...@bama.ua.edu] För Edward Jaffe
> Skickat: den 11 februari 2009 00:19
> Till: IBM-MAIN@bama.ua.edu
> Ämne: Re: SV: JCL job execution order
>
> Thomas Berg wrote:
> > Others have suggest
"David Andrews" wrote in message
news:<1234303549.427.231.ca...@chuck.duda.com>...
> On Tue, 2009-02-10 at 16:29 -0500, Dave Salt wrote:
> > It's very important that the jobs execute in the same sequence in
> > which they were submitted.
>
To combine 2 previous answers:
>Briefly ignoring Mark'
At 13:39 -0800 on 02/10/2009, Edward Jaffe wrote about Re: JCL job
execution order:
This is easy with JES3; difficult nee impossible with JES2. If the
environment is JES2, I suggest you have the last step of each job submit
the next one.
The simplest method (as others have stated) is to have
Edward Jaffe wrote:
Thomas Berg wrote:
Others have suggested that AAA ends with submitting BBB, etc.
But:
- If AAA abends before the submit step, should BBB be submitted in
that case also ?
- Sometimes even COND=EVEN doesn't help (no pun intended).
Maybe the variant where AAA *starts* with su
, 2009 1:30 PM
To: IBM-MAIN@bama.ua.edu
Subject: JCL job execution order
I'm trying to help someone create a process that will automatically
submit several jobs at a time. For example, it might submit 20 jobs
right after each other, with only a fraction of a second between each
job. It's very
Thomas Berg wrote:
Others have suggested that AAA ends with submitting BBB, etc.
But:
- If AAA abends before the submit step, should BBB be
submitted in that case also ?
- Sometimes even COND=EVEN doesn't help (no pun intended).
Maybe the variant where AAA *starts* with submitting BBB
would w
On Tue, 10 Feb 2009 17:05:49 -0500, David Andrews wrote:
>On Tue, 2009-02-10 at 16:29 -0500, Dave Salt wrote:
>> It's very important that the jobs execute in the same sequence in
>> which they were submitted.
>
>Briefly ignoring Mark's plea to consult the archives (sorry Mark), you
>might conside
rg Specialist IT-U SWEDBANK
> -Ursprungligt meddelande-
> Från: IBM Mainframe Discussion List
> [mailto:ibm-m...@bama.ua.edu] För Dave Salt
> Skickat: den 10 februari 2009 22:30
> Till: IBM-MAIN@bama.ua.edu
> Ämne: JCL job execution order
>
> I'm
On Tue, 2009-02-10 at 16:29 -0500, Dave Salt wrote:
> It's very important that the jobs execute in the same sequence in
> which they were submitted.
Briefly ignoring Mark's plea to consult the archives (sorry Mark), you
might consider reducing the number of JES2 converter subtasks to 1. If
you ha
We just have this discussion very recently?
I just checked... it wasn't all that recent - May 2008.
Dave, search the archives for "Controlling the execution sequence
of dependant [sic] jobs in JES2" so we don't rehash the entire
discussion again.
Mark
--
Mark Zelden
Sr. Software and Systems
...@bama.ua.edu] On Behalf Of
Dave Salt
Sent: Tuesday, February 10, 2009 1:30 PM
To: IBM-MAIN@bama.ua.edu
Subject: JCL job execution order
I'm trying to help someone create a process that will automatically submit
several jobs at a time. For example, it might submit 20 jobs right after each
On
> Behalf Of John McKown
> Sent: Tuesday, February 10, 2009 3:43 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: JCL job execution order
>
> On Tue, 10 Feb 2009 16:29:40 -0500, Dave Salt
wrote:
>
> >I'm trying to help someone create a process that will automatic
On Tue, Feb 10, 2009 at 1:29 PM, Dave Salt wrote:
> I'm trying to help someone create a process that will automatically submit
> several jobs at a time. For example, it might submit 20 jobs right after
> each other, with only a fraction of a second between each job. It's very
> important that the
On Tue, 10 Feb 2009 16:29:40 -0500, Dave Salt wrote:
>I'm trying to help someone create a process that will automatically submit
several jobs at a time. For example, it might submit 20 jobs right after
each other, with only a fraction of a second between each job. It's very
important that the job
Discussion List
To
IBM-MAIN@bama.ua.edu
cc
Subject
JCL job execution order
I'm trying to help someone create a process that will automatically submit
several jobs at a time. For example, it might submit 20 jobs right after
each other, with only a fraction of a second between each job.
Dave Salt wrote:
I'm trying to help someone create a process that will automatically submit
several jobs at a time. For example, it might submit 20 jobs right after each
other, with only a fraction of a second between each job. It's very important
that the jobs execute in the same sequence in
I'm trying to help someone create a process that will automatically submit
several jobs at a time. For example, it might submit 20 jobs right after each
other, with only a fraction of a second between each job. It's very important
that the jobs execute in the same sequence in which they were sub
38 matches
Mail list logo
