DSXchange

hi,

My job got aborted due to network issue i a need to recompile in order to re run it. I want to know why it is always necessary to recompile if a job aborts, is there any specific reason???

The assumption on which your question is predicated is false. It is not necessary to recompile after a job aborts.

It is sufficient to reset. This is a special run mode, to get things back to as they were (as far as is possible) as at the start of the aborted run.

Hi...
It is not necessary to recompile the job, if it is failed..

Even if you reset the job , job can run.
Compile is needed if you are doing any change to job..

hope this helps

Katie09 wrote:Hi...
It is not necessary to recompile the job, if it is failed..

Even if you reset the job , job can run.
Compile is needed if you are doing any change to job..

hope this helps

But all these things can be done through director only. From designer if a job is in aborted state it won't let you run without compiling.

:D

priyadarshikunal wrote:From designer if a job is in aborted state it won't let you run without compiling.

Nothing stopping you from resetting it from the Director first. Regardless, the bottom line is what Ray noted, the assertion that "it is always necessary to recompile if a job aborts" is incorrect. It is never "necessary".

chulett wrote: Nothing stopping you from resetting it from the Director first.

I apologize for not explaining it correctly but I just wanted to make sure the person uses the director to reset it.

You can also use the command line interface dsjob to reset a job.