what happens internally when a job is reset
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 730
- Joined: Tue Nov 04, 2008 10:14 am
- Location: Bangalore
what happens internally when a job is reset
If a job aborts it is required eighter to reset it or compile it in order to rerun the job, why is this required, what happens when a job is reset which makes it eligible for re-run?
DataStage is designed so that when a job aborts it cannot be re-run again until it is reset. This is intentional so that a job cannot just continue to abort on subsequent runs without any noticing that it doesn't work. The "reset" of a job does nnot perform more than changing a status flag on the job, there is no cleanup or similar actiity involved.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
As well as what Arnd said, resetting a job will roll back any uncommitted transactions, disconnect from data sources, close files and hashed files, and generally return the job to the state it was in prior to the last run request (as nearly as possible - transactions already committed remain committed). It also changes the job's status to "has been reset" if successful and, where relevant, moves any unlogged messages from the &PH& directory into the job log.
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.