Schedule

This section contains task scheduling properties. Some default values of the displayed information can be modified. Refer to section: Task Default Settings.

• To modify a property, select it from the list and click Update.
• To delete a property, select it from the list and click Delete.
• To define a new property, click the appropriate button in the Schedule section toolbar.

Validity

Displays the "First schedule date": date from which the calculator will take into account the task’s schedule. The first launch will be generated at this date to run at a date determined by the task.

To change the task’s first scheduled date select the Validity line and click Update. In the Validity window enter:

• Valid from: Enter the required date or click the calendar button to select it from a calendar.
• To: If needed, check the box and enter the end of validation date for the task. No launches will be generated after this date. If the box is cleared, the task will continue generating launches.
• Click OK to validate.

If the validity date falls outside the calendar range, the Calculator will not be able to compute the next launch. The next launch will not be computed while the validity date is in the future.

Type of Launch Window

Select the line and click Update to modify the launch window type.

Type of Launch: Possible values are “Serial” or “Parallel”

• Serial: The next launch is not calculated until the end of the launch window. A launch window should always be inferior to the frequency of execution, otherwise launches will be lost.

Example: Frequency = 24 hours, launch window = 48 hours.

The calculator will wake up every 2 days to calculate a launch that should have taken place the day before.

• Parallel (introduced in V5.2, default value in V6): The next launch is calculated at the start of the launch window. The user can create as many launches as desired at their scheduled launch dates and times. On the other hand, only one launch will be retained in cases where two rules schedule an identical launch date and window.

Launch Window Definition: for scheduled and watcher tasks the user has the following choices:

• Multiple launch windows:
• Day dependent launch windows:
• Auto-Relaunch:

Launch window

To modify a launch window select the line and click Update to change the launch window.

To add a launch window (a task can have multiple launch windows on the same day) select Add > Launch Window in the toolbar of the Schedule section,

• Launch Window for a provoked task:

Select When requested to allow a provoked task to be condition checked on submission, or select From to define a specific launch window:

From: Contains the task’s launch window start time.

During … hours … min.: Contains the duration of the task’s launch window.

• Launch Window for a Cyclical task:

Use this type of window if the task must be launched cyclically starting with the validity date:

Every … hours … min.: Enter the launch cycle.

During … hours … min.: Enter the duration of the launch window.

• Multiple launch windows:

Use this window if the task is launched once a day, at the same time each day. Click At and enter:

Time: Enter the start time of the launch window.

Duration: Enter the duration of the launch window.

Use this window if the task must be launches several times per day. Click From. This function defines up to 1400 launches per day (one per minute):

Time: Enter the start time of the launch window.

Duration: Enter the duration of the launch window.

Every: Enter the interval between the start of each launch window.

Until: Enter the time beyond which no further launches will be calculated. The start time of the last calculated launch must be inferior to this limit.

Click OK.

More launches with a different interval can be added by creating a new multiple launch windows.

• Day dependent launch windows:

Use this window if the task is launched once a day but the launch window is required to vary with the day of the week (even if it is not scheduled every day).

From: Enter the start time of the launch window.

Duration: Enter the duration of the launch window.

Apply template for whole week: Click this button to apply the data entered for all days of the week.

The fields From and Duration can be modified and for all the days of the week.

Click OK.

• Auto-Relaunch:

Use this window if the task is to be systematically re-launched as soon as it finishes executing.

This launch window type is of no interest for a watcher task, because it remains watching during the whole launch window, even if it submits its session or its Uproc when resources arrive.

Time: Enter the start time for the first window.

Duration: Enter the duration of the task’s launch window.

Relaunch period: Enter the launch cycle.

Relaunch delay: Interval between the end of execution of the task (of the Uproc or all the Uprocs in the Session) and the creation of a new launch.

Auto-relaunch limit: Check this box to enter the maximum number of relaunches allowed for the task. If the box is not checked there will be no limit.

Add > Rule

A rule automatically calculates the date / time to launch this task.

Rule: Enter the scheduling rule code or click the arrow button to select it from the list.

Start date: Enter the required start date for applying the rule or click the calendar button to select it from a calendar.

End date: If the rule is temporary, check this box and enter the end date for applying the rule, if not, do not check this box.

The start date (application date) represents the reference to be applied to the rule for the Calculator. This date is the starting point of the cycle defined in the rule. It is recommended to set the start date as close as possible to the first scheduled date.

Launch time: Check this box to define a specific launch window for this rule. It will be added to the other launch windows.

• At: start time of the launch window
• Duration: duration of the launch window

Click OK to add this new rule to the task. Click Cancel to ignore the current operation. An automatic postponement may be applied by using Add > Offset Rule.

Add > Exclusion Rule

DUAS V6 only

An exclusion rule automatically calculates the date / time for which the launch of this task will be excluded.

• Rule: Enter the exclusion rule code or click the arrow button to select it from the list.
• Start date: Enter the required start date for the rule or click the calendar button to select it from a calendar.
• End date: If the rule is temporary, check this box and enter the end date for applying the rule, if not, do not check this box.
• Launch time: N/A

Click OK to add this new rule to the task. Click Cancel to ignore the current operation.

Add > Exception

Exceptions cover exclusions by date or interval and explicit launches.

Enter the required date or click the calendar button to select it from a calendar.

• Do not run on (Exclusion Date): No launch of this task will be scheduled for this date.
• Do not run (Exclusion Window): No launch of this task will be scheduled during the defined period.

Between: start date and time of the exclusion window

And: end date and time of the exclusion window

• Run at: Add an explicit scheduling date for this task without the use of a scheduling rule. An explicit date supersedes a date resulting from implicit schedule.

During: Duration of the launch window, this time frame can be as long as 999h59.

Processing date: The processing date associated with the launch (formatted according to the functional period of the Uproc referenced in the task). If the Uproc referenced in the task is defined without a functional period, this field is not displayed.

Add > Offset Rule

A systematic offset can be applied to the day calculated by the rule.

This offset applied to all the task rules.

This offset can be defined as the number of calendar, working, closed days or holidays, preceding or following the day calculated by the rule.

Check the box Include Offset so that the processing date associated with the launch corresponds to the day obtained by the offset rule. If the box is not checked, the processing date calculation will remain as defined in the Functional Data section.

For example:

If the Uproc has a Day functional period and if the rule calculates the first closed day of the month, the user can ask to offset to the next working day for this task. The calculated processing date would therefore be the first working day date following the first closing day of the month.

Add > Time Limit

DUAS V6 only

Kill execution: Enter the time (hour and minutes) beyond which any Uprocs associated with the selected task will be stopped. Depending on the launch status the next action will be executed:

• Launch wait: No immediate change in the status, however during the task submission, its status becomes Aborted.
• For all other statuses: The status is changed immediately and becomes Aborted.

When a time limit is added to a task with an Auto-relaunch launch window, the task will only execute once within the Auto-relaunch period and the job run will not be aborted. The next scheduling will occur the next day the task can execute according to the associated rule.

Export a Rule

In the Schedule, select a scheduling rule and click the button Export Rule from the toolbar to export the rule to the list of local rules.

It is not possible to export a rule in which the name already exists in the local rules list.

Current rule name: Displays the selected rule name as it appeared in the task.

Target rule name: Enter the rule name as it will be available in the local rule list.