Schedule Trigger Properties
The Schedule Trigger Properties window contains the settings for a Schedule Trigger.
Property Pages
Property pages common to all Triggers
General
Name for this trigger (optional)
Optionally, specify a descriptive name for the trigger.
Enabled
Uncheck this box to disable the trigger. If the trigger is not enabled, adTempus will ignore it (it will not cause the job to trigger).
Minimum Interval
Specify the minimum interval (in seconds) for this trigger. Once the triggers conditions are satisfied and the job is triggered, adTempus will ignore this trigger for the specified interval.
For example, suppose you are using a File Trigger to trigger the job whenever a new file is added to a folder. If you set the interval to 60 seconds, then once adTempus triggers the job, it will ignore any new files that arrive in the next 60 seconds.
Description/Notes
Enter any extended descriptive information or notes for this trigger.
Job Variables
The Job Variables page allows you to define Job Variables that will be set for this job only when it is started by this trigger.
Job Variable list features and tools
The Job Variable list shows variables defined for the current object as well as variables inherited from a higher level. Icons next to each variable in the list convey information about their inheritance:
|
The variable is inherited from a higher level |
|
The variable is inherited from a higher level and is locked (cannot be overridden) |
|
The variable is inherited from a higher level and has been modified at this level |
|
The variable is new at this level |
|
The variable is inherited from a higher level and must be overridden (a value provided) at this level |
|
The variable has been overridden (redefined) at a lower level. This icon only appears if you have analyzed variable usage (see below). |
When you hove the mouse pointer over the icon for an inherited variable, adTempus will show where the variable was inherited from.
Filtering the variable list
The variable list can be filtered to:
- Hide inherited variables (so you only see variables defined at this level)
- Hide variables that cannot be modified (inherited variables that are locked to prevent modification)
- Show only variables that must be overridden
Analyzing and viewing variable usage
5.0
When you click Analyze variable usage, adTempus searches for all the places where the variables are used or overridden. After this analysis is complete, new columns are added to the list to show, for each variable:
- Whether it has been overridden (redefined) at a lower level
- A count of how many times it is referenced (used)
Clicking Show variable usage opens a new window showing all the references and overrides for the variables. This is the same window shown by the Find Variable and Function References tool.
Analyze variable usage only finds references and overrides that are "below" the current level. For example, if you are viewing the variables for a job, this will find all references and overrides within the job, or within jobs that may receive variables from this jobs (jobs run by Responses or Job Triggers). If you are viewing a group, this will find all references and overrides within groups and jobs below the selected group. That is, the tool only lists places that might be affected by changes to the variables in the list.
This tool does not show other places where the variables might be used. For example if you are viewing job A and some of the variables are also used in job B, those uses will not be listed unless there is a link between job A and job B.
To find all references to a variable:
- If the variable is defined at the server level, use the Analyze variable usage tool from the variables list at the server level. This will show all uses everywhere in adTempus.
- Use the Find Variable and Function References tool to find a specific variable or all variables.
Schedules
On the Schedules page you specify the Schedules that determine when the job should be run. You may add, edit, or remove schedules.
If you have specified more than one schedule, each schedule will trigger the job independently. For example, if one schedule includes all Mondays and another includes all Tuesdays, the job will be triggered on Mondays and Tuesdays.
If the schedules have overlapping times, this will not cause the job to be triggered twice at the same time. For example, if Schedule 1 and Schedule 2 both call for the job to be run at 12:30 pm on Monday, the job will only be run once at 12:30.
See the Schedule Trigger Overview topic for more information on using multiple schedules versus multiple Schedule Triggers.
Options
On the Options page you specify clock change and time zone options for this trigger.
System Clock Changes
These settings determine what adTempus will do if changes to the computer's clock affect scheduled execution times for the job.
Rerun if clock is set back
If this option is checked, the job will continue to run at its regular schedule even if the clock is set back so that executions are repeated. If the option is not checked, any "repeated" times will be ignored.
For example, your job is scheduled to run at 1:30 every morning. At 1:32 am on 21 August 2002, just after the job has run, the system clock is set back to 1:29 am when the clock is synchronized with a master clock. If the Rerun... option is checked, the job will be run when the clock reaches 1:30 again. If the option is not checked, the job will not be run again until 1:30 the next day.
Guidance: If your job is only meant to run once a day, you will want to leave this option unchecked (the default setting). If, however, your job is meant to run at regular intervals (e.g., to transfer data every 5 minutes), you will probably want to check the option so that the job continues to execute regularly even when the clock is set back by an hour for daylight saving time.
Run once if clock is set forward so that one or more scheduled executions are missed
If this option is checked, adTempus will run the job once if a time change causes a regular execution to be missed. If the option is not checked, executions may be missed as a result of the time change.
For example, your job is scheduled to run at 2:30 every morning. At 2:00 one morning the system clock is set forward to 3:00 am due to daylight saving time. If the Run once... option is checked, adTempus will run the job when the time change is detected to make up for the missed time. If the option is not checked, the execution will be missed.
adTempus will only execute the job once, regardless of the number of executions that are missed. For example, even if your job runs every minute and the clock has been set forward by a full hour, adTempus will run the job once, not 60 times.
Guidance: If your job only runs once a day (or less frequently) you will want to check this option (the default setting) to ensure that the job gets run. If, however, the job runs frequently (e.g., once an hour) you may want to uncheck this option, as missing one execution is not likely to be significant.
Time Zone
The time zone setting determines which time zone adTempus should evaluate this trigger in.
Local time zone on the computer where the job is triggered
The trigger will be evaluated in the time zone of the where the job is triggered. That is, if the job is scheduled to run at 11:30 am, it will run at 11:30 am local time on the computer triggering the job.
Note: If this job is in a Distributed Scheduling queue, this option causes adTempus to use the time zone of the Controller computer for Basic and Load Balance queues (because the Controller triggers the job for these configurations). For Mirror queues, the time zone of the Agent that runs the job will be used.
A specific time zone
The trigger will be evaluated in the specified time zone. For example, if the job is scheduled to run at 11:30 am and you select the Pacific time zone, the job will run at 11:30 am Pacific time. If the server running adTempus is located in the Eastern time zone, the job will execute at 2:30 pm local (Eastern) time.
The time zone of the Controller with which the Agent is associated
This option is only available if you are configuring the job on a Distributed Scheduling Controller computer. When this option is selected, the time zone of the Controller will be used to evaluate the scheduled times, even for Mirrored jobs.
Holidays
On the Holidays page you specify how adTempus should treat this job if it is scheduled to run on a holiday.
Use the following set of holidays
If you want the job to behave differently on holidays, check this option and select the list of holidays that applies. You may optionally create or edit a holiday set if none of the existing sets meets your needs.
If you do not want the job to behave differently on holidays, uncheck this option.
When the job is scheduled to run on a holiday
Specify how adTempus should behave if a scheduled execution for the job falls on a holiday. The following options are available:
- Run as scheduled. The job is still run according to the schedule rules. Use this option if you using date selection rules to cause the job to run only on holidays or non-holidays. See the Date Rule Properties topic for more information.
- Don't run the job. The job is not run on any day that is defined as a holiday.
- Run the job on the nearest business day. The job is run on the nearest day that is not a weekend or holiday. This could be either before or after the originally scheduled date.
- Run the job on the previous business day. The job is run on the nearest prior day that is not a weekend or holiday.
- Run the job on the next business day. The job is run on the nearest subsequent day that is not a weekend or holiday.
- Run the job on the nearest non-holiday. The job is run on the nearest day that is not a holiday. This could be either before or after the originally scheduled date and could be a weekend.
- Run the job on the previous non-holiday day. The job is run on the nearest prior day that is not a holiday (but may be a weekend).
- Run the job on the next non-holiday. The job is run on the nearest subsequent day that is not a holiday (but may be a weekend)
Related Concepts
Related Topics
Reference