View previous topic :: View next topic |
Author |
Message |
kingofbeasts Beginner
Joined: 23 Sep 2003 Posts: 5 Topics: 2
|
Posted: Mon Jan 05, 2004 4:19 am Post subject: Two jobs in a member |
|
|
Hi,
I have two Jobs in a PDS member. When Job is submitted, the two jobs will be executed. I want to execute the first job and stop the execution of the second job.
The JCL looks like,
//jobname1 job (,).....................
//.............................................
//step000.................................
//.............................................
// (null statement)
//jobname2 job (,).....................
//.............................................
//step001.................................
//.............................................
Please suggest, if there is any command to end the first job after the execution or stop the execution of the second job.
Thanks in advance, |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12375 Topics: 75 Location: San Jose
|
Posted: Mon Jan 05, 2004 10:04 am Post subject: |
|
|
Kingofbeasts,
Can you edit the PDS member containing the 2 jobs? Just code TYPRUN=HOLD on the second jobcard and this will job will be in queue until you release it. You will have a choice either to release it or cancel the job.
On second thoughts why don't you seperate the 2 jobs and make each job as one member?
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
kok328 Beginner
Joined: 05 Nov 2003 Posts: 19 Topics: 0 Location: MI, USA
|
Posted: Mon Jan 05, 2004 1:51 pm Post subject: |
|
|
Better yet, just put a // after the first job and before the second job. |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12375 Topics: 75 Location: San Jose
|
Posted: Mon Jan 05, 2004 3:21 pm Post subject: |
|
|
kok328,
If you carefully look at the the JCL posted you will find that there is indeed a NULL statement seperating the 2 jobs. However the null statement will no have effect on the execuetion of the next job. The null statement can be used to stop in between steps but not between jobs.
kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
kok328 Beginner
Joined: 05 Nov 2003 Posts: 19 Topics: 0 Location: MI, USA
|
Posted: Mon Jan 05, 2004 3:34 pm Post subject: |
|
|
kolusu,
I stand corrected....sorry, haven't been employed for a while now and am starting to forget and advise from fading memory. Perhaps it's time for me to hang up my keyboard. |
|
Back to top |
|
|
Mervyn Moderator
Joined: 02 Dec 2002 Posts: 415 Topics: 6 Location: Hove, England
|
Posted: Mon Jan 05, 2004 4:17 pm Post subject: |
|
|
Don't do that. Just don't shoot from the hip. _________________ The day you stop learning the dinosaur becomes extinct |
|
Back to top |
|
|
RobertL Beginner
Joined: 18 Nov 2003 Posts: 22 Topics: 0 Location: Lisbon, Portugal
|
Posted: Tue Jan 06, 2004 7:23 am Post subject: |
|
|
Assign a label at the end of job1 (for example .B), then enter the command
Only the first job will be submitted.
Regards,
Robert |
|
Back to top |
|
|
Dibakar Advanced
Joined: 02 Dec 2002 Posts: 700 Topics: 63 Location: USA
|
Posted: Tue Jan 06, 2004 7:33 am Post subject: |
|
|
Robert's method is cool, but I really wonder how IBM ever thought that people will ever need option like this. |
|
Back to top |
|
|
|
|