|
View previous topic :: View next topic
|
| Author |
Message |
athulvijay
New User
.jpg)
Joined: 01 Jul 2010
Posts: 17
Location: PUNE
|
|
|
|
| I need to submit 10 jobs in parallel; there jobs are for different purpose but should be submitted together, I do not want to submit it manually nor combine it in a single job. Is there any way to get this done using a JCL? All 10 jobs will be called inside a JCL so that submitting master jcl will execute all 10 jobs? |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Quote: |
| All 10 jobs will be called inside a JCL so that submitting master jcl will execute all 10 jobs? |
You do NOT understand JCL. Each job, once submitted, runs in an independent address space and there is no such thing as "calling a job" -- once submitted, the job either runs (or doesn't) totally apart from every other job in the system.
Use your site job scheduler (CA-7, Tivoli, Zeke, or whatever) to submit all 10 jobs. |
|
| Back to top |
|
|
athulvijay
New User
Joined: 01 Jul 2010
Posts: 17
Location: PUNE
|
|
|
|
Thanks alot Rob for the info. The below jcl helped me. Even though it do not completely serve my purpose but I am able to submit a Job inside a JCL.
//ASNP7C01 JOB ,'ASNP7C01',CLASS=A,TIME=1440,
// NOTIFY=&SYSUID,
// MSGCLASS=Q
//*
//JCLLIB JCLLIB ORDER=(DATAEV4.CMM.DEV.JCL)
//*
//ASNP7C01 EXEC PROC=CMM3025D
//ASNP7C02 EXEC PROC=CMM3055D |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
First - his name is Robert - not Rob. . .
What you show does NOT sibmit a JOB inside a JCL. You really need to learn to use the proper terminology . . .
What you show will execute 2 PROCedures one behind the other. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Your topic has been split into a new topic for this question.
| Quote: |
| Even though it do not completely serve my purpose but I am able to submit a Job inside a JCL. |
If you clearly explain your purpose, someone will have a suggestion . . . |
|
| Back to top |
|
|
athulvijay
New User
Joined: 01 Jul 2010
Posts: 17
Location: PUNE
|
|
|
|
Thanks alot Dick Scherrer for the suggestion.
CMM3025D, CMM3055D are my JCLs residing at DATAEV4.CMM.DEV.JCL. As you said second jcl will be executed only after successful completion of the first. My aim is to execute all JCLs at same time with out using any scheduler.
Aplogies for using wrong terminology. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
from the terminology You used and the scarce understanding of JCL
You might feel more comfortable posting here
ibmmainframeforum.com/index.php
the beginners forum |
|
| Back to top |
|
|
David Robinson
Active User
Joined: 21 Dec 2011
Posts: 199
Location: UK
|
|
|
|
| If the JCL that you submit has multiple jobcard statements in it, then multiple jobs will be submitted. Wont that acheive what you want? |
|
| Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2455
Location: Hampshire, UK
|
|
|
|
| Quote: |
| CMM3025D, CMM3055D are my JCLs |
More correctly these are your procedures. The way you worded your post makes it seem that the statements before your first 'EXEC PROC=' are not JCL. They are. And the whole shebang is normally referred to as a job although it is often referred to as 'a JCL' which is semantically wrong as it expands to 'a Job Control Language'.
What you have at the moment is serial execution - each procedure is executed one after the other. The only way to have parallel execution is to have 10 jobs, all with different jobnames and using different datasets (unless DISP=SHR is on common data datasets). You can have all 10 jobs in one member so that you only have to type SUB once. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
We still do not understand "your purpose" - other than you want to run all of these "at the same time".
Why will you not accept running them serially? What business or technical reason is there to run them all at once? And no, this is Not the "requirement".
The more you try to run concurrently, the more performance impact you generate for the system. |
|
| Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006
Posts: 1042
Location: Richmond, Virginia
|
|
|
|
Besides, as stated earlier, you have no control over when they actually execute, even though you might submit them at the same time.
One job, e.g., might be blocked from a dataset by a job not part of your jobs, over which you therefore have no control.
Or the initiator structure might not be what you need.
Etc. etc. etc................... |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
guess it is time to lock the topic...
it is getting nowhere  |
|
| Back to top |
|
|
Pete Wilson
Active Member
Joined: 31 Dec 2009
Posts: 580
Location: London
|
|
|
|
Split it into two jobs, within the same member and submit the one member as per below. Both jobs will be submitted for execution at the same time, but as mentioned they may or may not run concurrently due to initiator constraints or whatever.
//ASNP7C01 JOB ,'ASNP7C01',CLASS=A,TIME=1440,
// NOTIFY=&SYSUID,
// MSGCLASS=Q
//*
//JCLLIB JCLLIB ORDER=(DATAEV4.CMM.DEV.JCL)
//*
//ASNP7C01 EXEC PROC=CMM3025D
//ASNP7C02 JOB ,'ASNP7C01',CLASS=A,TIME=1440,
// NOTIFY=&SYSUID,
// MSGCLASS=Q
//*
//JCLLIB JCLLIB ORDER=(DATAEV4.CMM.DEV.JCL)
//*
//ASNP7C02 EXEC PROC=CMM3055D |
|
| Back to top |
|
|
|
|
