 |
|
An important part of DMT is its powerful scheduler. All exports and loads can be scheduled to run at chosen dates, times or interval. To control when exports and loads are run by the scheduler, all groups and jobs have a set of scheduling parameters.
Scheduling parameters are composed of various fields depending on the scheduling frequency selected.
Last Run: This field shows information about the last run of the group or job. Click on the button on the right ( 
) to open the LRI Form and see more information.
Begin and End: These 2 fields are optional and allow you to delimit the time period during which a group or job will be scheduled. Outside this time period, a group or job will not be run by the scheduler.
In all the examples below, the time period is set from January 1st 2010 to December 31st 2010 (note that the date format can be changed in the Settings Tab).
Click on the arrow on the right hand side of the fields to open a calendar and easily choose a date.
This is a special value that prevents a group or job to be run by the scheduler.
Use it value when you want a particular group or job to only be run manually.
 |
The group or job is run continually at a specified interval.
 |
Max Num. of Runs: Maximum number of times the group or job is allowed to run. Every: Time interval (Hours : Minutes : Seconds) at which the group or job must run. If set to 01:00:00 the group or job will run every hour. On Following Day(s): Allows you to specify the days when the group or job should or shouldn't run. |
The group or job is run once a day at a specified time.
 |
Max Num. of Runs: Maximum number of times the group or job is allowed to run. Every: Allows you to choose the number of days to wait before running the group or job again. e.g. "Every 1 Day(s)" runs every day. "Every 2 Day(s)" runs every other day, etc. At: Time at which to run the group or job. On Following Day(s): Allows you to specify the days when the group or job should or shouldn't run. |
The group or job is run once a week at a specified time.
 |
Max Num. of Runs: Maximum number of times the group or job is allowed to run. Every: Allows you to choose the number of weeks to wait before running the group or job again. e.g. "Every 1 week(s)" runs every week. "Every 2 Week(s)" runs every other week, etc. At: Time at which to run the group or job. On Following Day(s): Allows you to specify the days when the group or job should or shouldn't run. |
The group or job is run once a month on a specified day at a specified time.
 |
Max Num. of Runs: Maximum number of times the group or job is allowed to run. Every: Allows you to choose the day of the month when the group or job runs. e.g. "Every 1 of the Month" runs every first day of the month. At: Time at which to run the group or job. On Following Month(s): Allows you to specify the months when the group or job should or shouldn't run. |
The group or job is run once a month on a specified day at a specified time.
This frequency is similar to Monthly 1 but gives you more flexibility in selecting the day to run.
 |
Max Num. of Runs: Maximum number of times the group or job is allowed to run. Every: Allows you to choose the day of the month when the group or job runs. It's composed of two parts (see below). At: Time at which to run the group or job. On Following Month(s): Allows you to specify the months when the group or job should or shouldn't run. |
By combining these two values you can choose virtually any day of the month. e.g.
The load is started immediately after the export group or job it's linked to has completed.
This is useful when you want to transfer data from one place to another (i.e. export + load in one seamless operation).
 |
Max Num. of Runs: Maximum number of times the group or job is allowed to run. |
Note: This scheduling frequency is only available for Load groups or jobs that are linked to an export group or job (see 6.2. Load Group or Job Parameters).
Note: This scheduling frequency is only operational when Groups or Jobs are run by the scheduler. e.g. If you run an Export job from the DMT client and a load job is linked to this job with an "After Export" scheduling frequency, the load job will not be run automatically after the Export Job.
|
|
|