DSXchange

Hello,

I am in the testing phase of a project.

Is reset in director same as compile in designer?

It takes less time for me to reset the job in director than open jobs in the designer and compile if the jobs abort. I am running these jobs using a batch job

Thanks & Regards,
RL

Hi,

I searched and found this link

viewtopic.php?t=129605&highlight=compile++reset

The jobs aborted because the input files were present at the time of run, in this case 'reset' is a good option as jobs were not changed.

'Compile'was applicable if there was a code change
Please correct my understanding (in this scenario) if I am wrong

Thanks & Regards,
RL

Compiling a job generates the OSH.If a job is reset,the OSH is not created.After reseting a job,it comes into "runable" state.

Note:If a job is recompiled,OSH is generated only for the changed components.

Resetting a job is only a change in state of the executable.

Thank you all for explaining it at the OSH level.

RL

There's no "OSH" in a Server job.

chulett wrote:There's no "OSH" in a Server job. ...

Hi chulett,

if a job is reset the basic program is not changed and only the executable state will be changed so that the job can be run.
and if a job is compiled the basic program will be updated

is it correct?

thanks
rl

Correct. You could remove the word 'BASIC' from what you wrote and have a statement applicable to either job type. Reset is for status, compile... compiles. As in the 'executable', whatever it is - BASIC, C++, OSH, etc.