A job which was in "Aborted" state, started running when initiated through a sequence.
Usually when a job is in "not compiled/Aborted/failed validation" state, the sequence will also abort.
But I wonder how a job in Aborted state started running without the sequence getting aborted.
Can anyone clarify me?
Aborted Job started running in a sequence
Moderators: chulett, rschirm, falsehate
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Master Data Management is a separate group of products from DataStage, so you have not posted in the correct forum.
The answer is almost certainly that the Job activity in the sequence specifies "reset if required, then run".
The answer is almost certainly that the Job activity in the sequence specifies "reset if required, then run".
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.