Restart Datastage Job/Sequence

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
balu536
Premium Member
Premium Member
Posts: 103
Joined: Tue Dec 02, 2008 5:01 am

Restart Datastage Job/Sequence

Post by balu536 »

Hello Everyone,
I don't know whether this topic is already discussed, but i couldn't find it in the search list.

I have a datastage sequence which contains 10 jobs and say suppose in 3 rd(source having 10000 records) job after loading 9000 records to target, job got aborted.

Now when restarting the sequence, i want the sequence to be re-started from the 9001 record in 3rd sequence rather than restarting the 3rd sequence from first record.

Please help me on this.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

It has been discussed a number of times in the past. Basically you have to design the 3rd job so that it can pick up where it left off - there is no automatic mechanism for achieving this. The design, clearly, involves some kind of persistent "remembering" which rows have been processed successfully.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

And will also require a static source.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Part of the restartability design might well involve capturing a snapshot that you can use when restarting.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kduke
Charter Member
Charter Member
Posts: 5227
Joined: Thu May 29, 2003 9:47 am
Location: Dallas, TX
Contact:

Post by kduke »

This is easily solved if insert and update is decided in the current job. Too many people decide this in a prior job and then write out a insert dataset and a update dataset. This will always cause problems if you ask me.
Mamu Kim
Post Reply