Machine priority force start issue

[marcovan]

Hello, 

Have various jobs that use multiple machines in the definition, example:  machine:  macha, machb.   Have defined macha with a factor of 1.0 and machb with a factor of 0.8 so that macha has priority.  This has been working except when there is a need to force start a job.  When force starting it ignores factor so it will try to run on machb or machb as it ignores factor values.

Is there any other way that when forcestarting a job, we force to run on macha as opposed to machb?

Thanks

[Jose Lopez]

Hi,

Have you tried to run jobs on a virtual machine instead of a pool or real machines?

Best regards.
José

[Leroy Zine]

 I think there's an option now in the config file.   Read up on the "UseMachineMethodOnForceStartJob" parameter.

However, if you don't want to make any changes to the jobs, machine definitions or the config file, you can try this.  If the jobs are in a box and the box is still running, you can just put the failed job On Hold and then Off Hold and it will start by it's normal process of selecting a machine.  If the job has date conditions in the box, you'll also need to do a one time override and change the date conditions to 0 prior to taking it Off Hold.

  If the job isn't in a box, you'll need to do a one time override and change the date conditions to 0 (if it has it) and then issue a STARTJOB on it instead of a FORCE_STARTJOB.

------------------------------
AutoSys Administrator
Bank of America
------------------------------