My requirement is to call three datastage jobs through a unix shell script. Shell script will call one job after another.
But if any job aborts, then during re-run shell script should start running the jobs from point of failure.
Example:
Shell script is calling Datastae jobs
A -> B -> C
If A completed successfully and B got aborted then during re-run shell script should run only jobs B and C.
We really do not want to create any temporary file on Unix to store status of jobs.
Could you please help me.
Restartability while running multiple Datastage jobs through
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 20
- Joined: Mon Dec 11, 2006 10:57 am
- Location: Pune
Restartability while running multiple Datastage jobs through
Mayur Dongaonkar.
-
- Participant
- Posts: 20
- Joined: Mon Dec 11, 2006 10:57 am
- Location: Pune
-
- Participant
- Posts: 20
- Joined: Mon Dec 11, 2006 10:57 am
- Location: Pune
Why not keep it between a single Master Sequence and multiple jobs in it? The only thing that you will do from UNIX is to call dsjob to execute the master sequence. This way you can use your enterprise scheduler, and at the same time, have a single entity (Master Sequence) to monitor and manage.Mayur Dongaonkar wrote:We want to keep it between single Unix shell script and multiple Datastage jobs in it.
Instead of spending time on changing your UNIX script, why not allocate that time to building a restartable sequence? Its more maintainable, and I assure you it won't take long.
But then, that's how I see it, others may wish to differ.
gateleys
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Then you're on your own. DataStage provides a tool: you choose not to use it.Mayur Dongaonkar wrote:We want to keep it between single Unix shell script and multiple Datastage jobs in it.
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.