Hi All,
Is there any DataStage Macro/variable that can be used inside the Sequence, to determine if that particular run is normal run or a restart.
Thanks in Advance.
Restart variable in Sequence
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
No.
You could look at the job sequence log in Director (or using API functions or dsjob command) - from memory a regular run request has "job run requested" while a reset has something different.
You could look at the job sequence log in Director (or using API functions or dsjob command) - from memory a regular run request has "job run requested" while a reset has something different.
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.
Thanks Ray.ray.wurlod wrote:No.
You could look at the job sequence log in Director (or using API functions or dsjob command) - from memory a regular run request has "job run requested" while a reset has something different. ...
What i am trying to accomplish here is, if the Sequence is executed from a previous abort(if i can determine if it is a Restart, from within the Sequence), i would like to execute a job which deletes the data from a table that got partially loaded.
If i can not determine if it is a Restart, from within the Sequence, is there a 'Before' stage command in OracleEnterprise stage to do the cleanup for the partial loaded table, in case of a restart?
I would like to cleanup the data that is already partially loaded into that table and rerun the same job.
Thanks in Advance.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Try to implement some logic as such
At the start of the sequencer, create an empty file. delete this file on successful completion of the sequencer. can use after-jopb subroutine.
When starting the sequencer, try to see if file is present. If its present it means the seq is restarted after abort - call your delete jobs and clean the table. conversely if the file is not present, then it means your sequencer has run properly.
At the start of the sequencer, create an empty file. delete this file on successful completion of the sequencer. can use after-jopb subroutine.
When starting the sequencer, try to see if file is present. If its present it means the seq is restarted after abort - call your delete jobs and clean the table. conversely if the file is not present, then it means your sequencer has run properly.