I have a sequencer which in turn calls 5 other sequencers,few routine activity stages,User variable stage and wait for file activity.
all four options namely Add checkpoints,Automatically handle activities that fail,Log warnings,Log report messages after each job run is checked in the main sequencer and in sequencers called by the main sequencer.Wait for file is made not to checkpoint run.
If the sequencer aborts at some point and i restart the sequencer without resetting it,it doesn't start from the check point.
The sequencer starts, skips the run of job1,and first routine activity and goes to finished state.Its not checking the status of other checkpointed run jobs though there few other jobs that have completed successfully.
Sequencer not restarting from check point
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 26
- Joined: Tue Dec 18, 2007 6:31 am
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Re: Sequencer not restarting from check point
why this is not with checkpoint? Any specific reason?harish_s_ampeo wrote:Wait for file is made not to checkpoint run.
Try after changing it and post the results.
Regards,
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.![Wink :wink:](./images/smilies/icon_wink.gif)
Genius may have its limitations, but stupidity is not thus handicapped.
![Wink :wink:](./images/smilies/icon_wink.gif)
-
- Participant
- Posts: 26
- Joined: Tue Dec 18, 2007 6:31 am
Re: Sequencer not restarting from check point
The wait for file is to abort the sequencer if the file didn't arrive within the time out period and trigger the exception handler .But once we receive the file we will just restart the sequencer so that it checks for the file and triggers the jobs that follow the Wait for file activity.
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Re: Sequencer not restarting from check point
Anyways if the file is not present it will not trigger the sequence after that and will restart from that acivity itself as its the point of failure.harish_s_ampeo wrote:The wait for file is to abort the sequencer if the file didn't arrive within the time out period and trigger the exception handler .But once we receive the file we will just restart the sequencer so that it checks for the file and triggers the jobs that follow the Wait for file activity.
Hence even if you enable checkpoint on that activity it should work.
By removing checkpoint from that acivity you are forcing the sequnce to start from that activity, so why are you expecting it to start from point of failure.
Test after changing that and post the result whether its behaving as expected or not.
Regards,
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.![Wink :wink:](./images/smilies/icon_wink.gif)
Genius may have its limitations, but stupidity is not thus handicapped.
![Wink :wink:](./images/smilies/icon_wink.gif)
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Restart only skips leading checkpointed activities, not all checkpointed activities. Restart is from the first activity that does not have a checkpoint, resulting from unsuccessful completion. ("Do not checkpoint run" activities are executed, but later checkpointed activities can still be skipped.)
For example, if your sequence contains seven activities A1 through A7, A1 is marked "do not checkpoint run", then A5 fails. On restart, A1 will run, A2 through A4 will be skipped, then A5 will run. What happens after that depends on the exit status of A5.
For example, if your sequence contains seven activities A1 through A7, A1 is marked "do not checkpoint run", then A5 fails. On restart, A1 will run, A2 through A4 will be skipped, then A5 will run. What happens after that depends on the exit status of A5.
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.