The difference between run and reset if request then run

[dongyingying]

Hi

I a newcomer of the datastage ,Who can help to tell The difference between run and reset if request then run.

[ray.wurlod]

Run will attempt to run the job without checking its status. If the job aborted on its previous run it will fail to start, with the error "not in a runnable state (Aborted)".

Reset if required then run will check the job status first. If the job aborted on its previous run, it will be reset and only then will its normal run request be issued.

Of course, if you have not corrected the cause of the original failure, the job will fail again, but at least it will get started.

[chandra.shekhar@tcs.com]

By default you can keep it "reset if request then run". This is what we have used.

[kandyshandy]

Ok... Chandra told and i am going to stick to this forever

"Reset if required then run" is better than "run". Ray has given you the reason as well. If a job aborts, it will be reset & run automatically during the next batch run. Got it? Otherwise, it is a trouble!!

[chulett]

You need to decide which one is appropriate for each job being run. You may want to ensure that Aborts are resolved manually before restarting or you may be fine with them automatically resetting. Like many things... it depends.