View previous topic :: View next topic
|
Author |
Message |
naveensri2005 Currently Banned New User
Joined: 22 Mar 2005 Posts: 51 Location: chennai
|
|
|
|
hi guys,
in job I have 50 steps.the gdg dataset is creating in 1st step, the same gdg is refer in 25th step. I got abend in 24th step. Is it possible to restart from 25th step. If possible what are the changes we have to do? |
|
Back to top |
|
|
radhakrishnan82
Active User
Joined: 31 Mar 2005 Posts: 435 Location: chennai, India
|
|
|
|
If its a non-scheduled job then while restarting you need to refer step25 GDG's generation with(+0) or else you can delete the current generation(created in first step) and can restart the job if you dont want to do any changes to job.
If it is a scheduled job running thru CA7,then there is no need to change anything.You can restart from the aborted step. |
|
Back to top |
|
|
Rupesh.Kothari
Member of the Month
Joined: 27 Apr 2005 Posts: 463
|
|
|
|
Hi,
I agree with Radhakrishnan for his statement regarding Non Schedule job,
Quote: |
If it is a scheduled job running thru CA7,then there is no need to change anything.You can restart from the aborted step. |
NO, You have to change the GDG version from (+1) to (0) version in JCL throught CA7 and submit the JCL from Aborted step i.e step24.
http://ibmmainframes.com/viewtopic.php?p=6672#6672
Regards
Rupesh |
|
Back to top |
|
|
radhakrishnan82
Active User
Joined: 31 Mar 2005 Posts: 435 Location: chennai, India
|
|
|
|
rupesh,
In our shop,we run scheduling jobs thru CA-7.In such case,we normally dont disturb GDG's.
Quote: |
You have to change the GDG version from (+1) to (0) version in JCL throught CA7 and submit the JCL from Aborted step i.e step24. |
no need to change the version from your end.
Quote: |
For scheduling systems,the version (+1) is applicable during restart. Scheduling systems belong to the second case where in which your job flow STOPS during aborts.
If you mean to say that your job flow terminates with ur submitting id after the abort then as per case 1,version (0) is applicable.It is same as submitting a new job.hence (0) is applicable for GDG's during restart. |
For non-scheduling job,flow terminates.
In scheduling systems,job flow STOPS in case of abort.It will be in the abort queue (still the sytem support people responds to it).
GDG (+1) still points to current one created inside the scheduling job.
hope this helps. |
|
Back to top |
|
|
MGIndaco
Active User
Joined: 10 Mar 2005 Posts: 432 Location: Milan, Italy
|
|
|
|
If I can suggest my opinion, is better allocate the final gdg at the end of the job and not at the begin... but it's only a my opinion.... |
|
Back to top |
|
|
prasanth_thavva
New User
Joined: 28 Jul 2005 Posts: 86 Location: Chennai
|
|
|
|
Hi ,
Quote: |
change the relative number +1 --> 0 and disp-old/shr
restart = step25 |
plz correct me if wrong...
all d best |
|
Back to top |
|
|
radhakrishnan82
Active User
Joined: 31 Mar 2005 Posts: 435 Location: chennai, India
|
|
|
|
For non-scheduling job, relative number 0 in step25 is correct in this case. |
|
Back to top |
|
|
ksivapradeep
New User
Joined: 30 Jul 2004 Posts: 95
|
|
|
|
Hi radhakrishnan,
what ever may be the thing the gdg version will be created after the end of the job so how can we give (0) in the 25th step if you give (+1) there it will deffinetly work |
|
Back to top |
|
|
radhakrishnan82
Active User
Joined: 31 Mar 2005 Posts: 435 Location: chennai, India
|
|
|
|
Quote: |
what ever may be the thing the gdg version will be created after the end of the job so how can we give (0) in the 25th step if you give (+1) there it will deffinetly work |
friend,
Within the job flow the GDG refers (+1).For non-scheduling jobs,in case of abort the flow terminates.Hence,according to this case,it should be represented as (0)for non-scheduling jobs.Its fine at my shop.
I agree with you for scheduling jobs.As their flow STOPS in case of aborts.While restarting, the job flow continues and the GDG still refers (+1) until the entire job ran fine.
Hope this helps. |
|
Back to top |
|
|
akshaiya
New User
Joined: 17 Sep 2005 Posts: 49
|
|
|
|
Quote: |
what ever may be the thing the gdg version will be created after the end of the job so how can we give (0) in the 25th step if you give (+1) there it will deffinetly work |
I dont agree with "whatever may be the thing".
There lies CA-7.it differs for scheduling and non-scheduling.Even I was thinking it wrongly like "whatever may be the thing".but i tested with the help of my team.flow of the job terminates in case u are submitting non-scheduling jobs(when aborts).where flow continues in case of scheduling systems. |
|
Back to top |
|
|
dneufarth
Active User
Joined: 27 Apr 2005 Posts: 420 Location: Inside the SPEW (Southwest Ohio, USA)
|
|
|
|
As the original questioner has not reponded to any of these answers, I'd say too little information is known to give any advice. We don't know if a scheduler or restart software is involved. We don't know if the dataset was cataloged in creation step, or subsequent step, or passed to oblivion.
To quote the famous programmer Jerry Maguire, "show me the JCL!"
Dave |
|
Back to top |
|
|
suman12
New User
Joined: 22 Sep 2005 Posts: 3
|
|
|
|
We can use Condition parameter in 25 step. But we have to use EVEN keyword.Even if the previous Step(24) abended abnormally, the current step(25) will be executed. |
|
Back to top |
|
|
nitin4.a
New User
Joined: 16 Aug 2005 Posts: 26
|
|
|
|
hi
suman i think by using this the abend problem will be solved but to restart
from 25th remains
for that in all the rest steps the condition shld be given like that it becomes true till 25th step then all the steps will be skipped
like if all the 24 steps are executing well then from second step u can give
cond=(0,eq)
that particular step will be skipped
regards
nitin |
|
Back to top |
|
|
Anbudan
New User
Joined: 07 Sep 2005 Posts: 26 Location: Germany
|
|
|
|
Hi
I agree with prasanth_thavva
This is the best solution for this question. |
|
Back to top |
|
|
MGIndaco
Active User
Joined: 10 Mar 2005 Posts: 432 Location: Milan, Italy
|
|
|
|
I can't understand how this post is so complicated...
I'm sure that it's a base of JCL, scheduled or not.
At my site we have introduced a standard that force users to create the gdg version at the end of each job(or its chain) to avoid this discussion and for what I see it's a very interesting standard.
The solution is only one that Prasanth_thavva said.
The real problem that I can see, and all of us have, is how to restart without using substitution and other manual activity at our site.
All comment are wellcome and correct me if I'm wrong. |
|
Back to top |
|
|
funmini
New User
Joined: 17 Sep 2005 Posts: 2
|
|
|
|
I agre with akshaiya & radhakrishnan82.we have to know which job it is.whether it is a non-scheduled or scheduled job ca7 run job.
Quote: |
what ever may be the thing the gdg version will be created after the end of the job so how can we give (0) in the 25th step if you give (+1) there it will deffinetly work |
Quote: |
I dont agree with "whatever may be the thing".
There lies CA-7.it differs for scheduling and non-scheduling.Even I was thinking it wrongly like "whatever may be the thing".but i tested with the help of my team.flow of the job terminates in case u are submitting non-scheduling jobs(when aborts).where flow continues in case of scheduling systems |
.I dont agree with sivapradeep.I think prasanth_thava should have told for non-scheduled one.Unless he is wrong.We shouldnt come to a conclusion for naveensri's query with his little info as Dave said.
we have to wait till naveensri replies whether its non-scheduled or scheduled one.In the meanwhile better check this by using test jcl.you may come to know the difference between job scheduled thru ca7 and non-scheduled one in this topic. |
|
Back to top |
|
|
ritakaur
New User
Joined: 19 Sep 2005 Posts: 13 Location: Belgaum
|
|
|
|
Even i am wondering why it went complicated.The query should have explained whether it runs in scheduling mode or non-scheduling mode.
As i knew,scheduling thru ca7 cant be changed each and every time.It needs special request for changing the version or anything in case of aborts. so ca7 has such function to take the GDG(+1) inside the job as current version even when aborts.this is all i know.
rita |
|
Back to top |
|
|
MGIndaco
Active User
Joined: 10 Mar 2005 Posts: 432 Location: Milan, Italy
|
|
|
|
I'd like to know how the poster of this topic has solved this problem.
I'm really curious... |
|
Back to top |
|
|
|