|
|
| Author |
Message |
rahul.banik
New User
Joined: 23 Jan 2007
Posts: 12
Location: Mysore
|
|
|
|
Suppose 2 jobs JOBA and JOBB are running in production through CONTROL M.Both the jobs will create a same file(generation).There is no dependency bet 2 jobs.Both the job has single step.
Suppose this file name is MAIL.FILE and it's current generation is G2.
First JOBA is triggered.When it will come to CONTROL M for execution CONTROL M will check the generation of this file. As the current generation is G2 so G3 is defined for this JOB right.
But due to some reason this job has been abended it will take 1 hour to resolve this problem.
In the mean time the 2nd job JOBB triggered and ran fine.As G3 generation is not yet created JOBB will create the G3 generation for the file MAIL.FILE.
After 1 hour the 1st Job JOBA is ready to run.
As we want both the generations created by JOBA and JOBB so what will be the instruction for JOBA?RESTART from this step OR RESUBMIT the JOB?
I think I'm able to describe the problem.I need your help. |
|
| Back to top |
|
 |
References
|
 Posted: Thu May 15, 2008 7:16 pm Post subject: Re: Difference between resubmit and restart |
|
|
|
|
dbzTHEdinosauer
Senior Member
Joined: 20 Oct 2006
Posts: 1374
Location: germany
|
|
|
|
| Quote: |
so G3 is defined for this JOB right.
|
I have no experience with control-m, but are you saying that instead of using the normal gdg syntax to create a new file (+1), your scheduler is defining the new dataset with file.name.g0003v000 syntax.
I don't think any scheduler would do that.
JOBA creates a new generation of File A.
JOBB creates a new generation of File A.
so, regardless of the execution sequence (and the apparent obsurdity of this setup), you will have 2 new generations of File A.
apparently some job inputs a concatenated
File A(0)
File A(-1)
if this is not what you are doing, let us know, because you disposition for the new gdg should be delete on abend, catglg on sucessful eoj.
thus a restart or a resubmit should not cause a problem. |
|
| Back to top |
|
|
| Moved: Thu May 15, 2008 8:58 pm by superk From JCL to Other Mainframe Topics |
rahul.banik
New User
Joined: 23 Jan 2007
Posts: 12
Location: Mysore
|
|
|
|
| Quote: |
JOBA creates a new generation of File A.
JOBB creates a new generation of File A.
so, regardless of the execution sequence (and the apparent obsurdity of this setup), you will have 2 new generations of File A.
|
I agree with this Dick.And FILEA is a normal gdg.For both the job declaration is like that
| Code: |
DSN=OUT.MAIL.FILEA(+1),
DISP=(NEW,CATLG,DELETE), |
Current generation of FILEA is OUT.MAIL.FILEA.G0002V00.
If JOBA execute successfully then OUT.MAIL.FILEA.G0003V00 will create.
And JOBB will create after successful run OUT.MAIL.FILEA.G0004V00.
But JOBA is abended so as per DISP parameter OUT.MAIL.FILEA.G0003V00 will not cataloged.Then after successful eoj of JOBB OUT.MAIL.FILEA.G0003V00 will cataloged not OUT.MAIL.FILEA.G0004V00.Correct me if i am wrong.
My question is after fixing the error of JOBA what iwill be the instruction?
RESTART the job from abending step or RESUBMIT the job from begining.
Actually I'm thinking that if we RESTART the job then CONTROL M will overwrite the file OUT.MAIL.FILEA.G0003V00 which was cataloged by JOBB. |
|
| Back to top |
|
|
|
|
