View previous topic :: View next topic
|
Author |
Message |
kiranps
New User
Joined: 03 Nov 2005 Posts: 6
|
|
|
|
Hi,
I have a scenario like this...
STEP1 exec pgm=pgm1
.......
STEP2 exec pgm=pgm2
.......
//
STEP3 exec pgm=pgm3
........
Now if for some reason i want to restart the job from STEP3, is it possible? My concern is about the null statement coded after STEP2.
Thanks & Regards,
Kiran P S |
|
Back to top |
|
|
sridevi2005
New User
Joined: 15 Sep 2005 Posts: 42
|
|
|
|
Hi Kiran,
You can't execute the statemets after null statement.
Thanks,
Sridevi |
|
Back to top |
|
|
kiranps
New User
Joined: 03 Nov 2005 Posts: 6
|
|
|
|
I am aware of the fact that the null indicator // is the end of a job. But my question was pertaining to restart of STEP3. Do you mean to say that in case of restarting from STEP3 also, the job won't execute STEP3?
Help is greatly appreciated... |
|
Back to top |
|
|
priyesh.agrawal
Senior Member
Joined: 28 Mar 2005 Posts: 1448 Location: Chicago, IL
|
|
|
|
kiranps,
Why cant try this running a sample job yourself.
In this case if u restart from step3, even coded a null statement before, job will get abended JCL Error... with restart step not found.
Regards,
Priyesh. |
|
Back to top |
|
|
mmwife
Super Moderator
Joined: 30 May 2003 Posts: 1592
|
|
|
|
Any data after the // is flushed, i.e. goes into the bit bucket, so it is never considered part of the job.
If you resubmitted your job (as suggested) you will be informed that the step (step3) does not exist or cannot be found or some such. |
|
Back to top |
|
|
|