Hi,
I would like to know is there any commands to mark a job sucessfull ?
ie. Finished
As we do for Stop/Reset ?
-Thanks
How to mark a job as FINISHED
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
thanks for all for your replies.
I am asking this because, take a example that I have a sequenc which calls five underlying jobs. Today If I faced a problem where out of 5 jobs 1 job failed.
Now the status of Sequencer is 'Aborted/Restartable' and also of the job which will be 'Aborted'.
Suppose I fixed it some way and trying dsjob -run command of that job. It go FINISHED.
But my sequencer is sitting with status as 'Aborted/Restartable', which is sure going fail in next run if I dont do reset now. Other way I am searching is to mark this job complete explicitly, by giving status as FINISHED, if there are any means. (Which I feel is right thing to do)
-Let me know If I have not confused you more.
I am asking this because, take a example that I have a sequenc which calls five underlying jobs. Today If I faced a problem where out of 5 jobs 1 job failed.
Now the status of Sequencer is 'Aborted/Restartable' and also of the job which will be 'Aborted'.
Suppose I fixed it some way and trying dsjob -run command of that job. It go FINISHED.
But my sequencer is sitting with status as 'Aborted/Restartable', which is sure going fail in next run if I dont do reset now. Other way I am searching is to mark this job complete explicitly, by giving status as FINISHED, if there are any means. (Which I feel is right thing to do)
-Let me know If I have not confused you more.
-Raj
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
No, you have missed one critical point. The restartable job sequence continues to believe that the job in question has aborted (never finished successfully) so will attempt to execute it - and probably succeed if you have fixed the job.
The only legal way around this is to reset or re-compile the job sequence itself, which will clear the checkpoint record that is a part of the job sequence (not a part of the underlying job).
The only legal way around this is to reset or re-compile the job sequence itself, which will clear the checkpoint record that is a part of the job sequence (not a part of the underlying job).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: