Execute Job Window

Right-click a job and select the Run... command

The Run command is used to submit a job to run immediately. This feature can be used to test the setup of a job, or to run an "on-demand" job.

The Execute Job window allows you to specify how the job will be run.

General Options

The General Options page contains basic execution options for the job

Ignore conditions for the job

If this option is checked, adTempus will ignore any conditions that are defined for the job (this forces the job to execute even if the conditions are not met). Conditions at the step level are not ignored (see next option).

Ignore conditions for individual steps

If this option is checked, adTempus will ignore any conditions that are defined for steps of the job (this forces the step(s) to execute even if the conditions are not met).

Force a new instance of the job if necessary

This option overrides the Multiple Instances option for the job, forcing adTempus to start a new instance of the job even if another instance is already running.

Override queue limits and force the job to run immediately

If this option is checked, adTempus runs the job immediately, even if the Queue to which it belongs is currently at its quota for the maximum number of concurrent jobs. That is, this option will force the Queue to exceed its limit if necessary.

Run only on Master

If this option is checked, adTempus runs the job only on the Master computer, even if the job is associated with Agents.

To run the job only on a specific agent, select the agent from the Agents list and use the Runcommand on the pop-up menu.

Force job to run on Master

If this option is checked, adTempus runs the job on the Master, even if the Queue's Run on Master option is not checked.

Save the selected options as the default options

When this box is checked, adTempus remembers your choices for all of the above settings (settings in the "Options" group) and makes them the default the next time you run a job manually.

Make the job visible on my desktop

This option is available only if you are running the Console on the same computer where the adTempus service is running. When this box is checked, it overrides the job's User Interaction settings and causes adTempus to run the job in your current Windows logon session, if possible. This ensures that you will be able to see any windows shown by programs that the job runs.

This option may not be available if the adTempus administrator has disabled it or depending on other adTempus settings.

Responses

Choose which Responses you want to execute (this option applies to Responses for the job and for steps within the job):

Execute Responses: All Responses are executed as normal.
Do not execute any Responses: No Responses will be executed.
Do not execute any Job Control Responses:All Responses will be executedexceptJob Control Responses (Responses that run, terminate, hold, or release a job or job step). Use this option if you do not want adTempus to execute any other jobs that are chained to the current job.

Checkpoint

Specify the checkpoint to pass to the job.

Steps

The options on the Steps page determine which steps adTempus will run.

Run the job from the beginning

The job will run as normal, with all steps executed.

Run the job from the specified step

Execution will begin with the selected step and continue to the end of the job. If you check Run only the selected step, the job will end after the selected step is run.

Steps that have been disabled are not listed.

Run only the selected steps

Only the steps you select will be executed. Steps will be executed in their original order (as listed here), but you may skip steps.

Steps that have been disabled are not listed.

Variables

The Variables page allows you to set or override Job Variables that have been defined for this job. Values you provide here are used only for this execution of the job.

Notes

The Notes page displays the extended description/notes saved in the job definition.

You may also specify comments for this instance of the job (for example, an explanation for why the job is being run at an unusual time). Comments are saved with the instance and can be viewed in the instance details.