Scheduling Jobs
Jobs can be scheduled to execute once, a specified number of times, or continuously. When you set up a job, for example, you can schedule the action to execute in different ways:
cla140
Jobs can be scheduled to execute once, a specified number of times, or continuously. When you set up a job, for example, you can schedule the action to execute in different ways:
- Repeatedly
- At a specific date and time, or after a period of time
- Based on day-of-the-week dependencies
- Based on the execution of another job, or the existence of a file, or an end-user decision to execute the action now or later
By default, jobs are scheduled to run always. This means, the jobs are executed whenever the asset management agent starts on the asset. In other words, the execution of asset jobs is dependent on the agent run. For example, if the asset management agent is scheduled to run once a day and the asset job is scheduled to run only on Thursday, the job will be executed when the agent starts on Thursday.
You can specify the scheduling options in two ways:
- At the time of creating the job, the New Job Wizard has a Set Scheduling button that lets you specify the scheduling options.
- After creating the job, you can right-click the job and select Scheduling from the context menu.
In both the cases, the Scheduling Options dialog appears where you can define the following:
- SchedulingSpecifies the frequency of a job.
- ConditionsSpecifies various conditions for the job. You can schedule the job to run within a time and date range or on specific days in the week.
- DependencySpecifies that the execution of a job is dependent on the successful completion of another job or the existence of another file. You can specify the maximum number of simultaneous executions of an action per scalability server and thus distribute the network load over a period of time using the job concurrency limit.
- Pre-JobSpecifies a condition that should be checked before running the job:
- Enable prompts for the end-users allowing them to cancel execution of a job.
- Enable a force execution after a certain number of executions.
- Map a network drive, which may be necessary for the job to run.
- Post-JobSpecifies the actions to be performed after the job is completed. You can schedule a restart of the computer or the automatic deletion of a job after completion.
- MiscellaneousSpecifies that the job can be run without any user interaction.
Note:
For more details about Scheduling and Scheduling Options dialog, see the DSM Explorer Help
.