Novell Documentation: ZENworks for Servers 3.0.2 - Using Intervals and Repeating Actions in Schedule Types

Using Intervals and Repeating Actions in Schedule Types

Some scheduling options are common to several schedule types. These options must be understood before you can effectively use them.

Using Intervals with Distributors

For any schedule type the has an interval, the event will not start until after the Distributor has re-read eDirectory. For example:

Daily: If the Distributor is refreshed before the current day's time window has passed, the event will run on the current day, then every day thereafter; otherwise, it will first run during that time window on the next day, then every day thereafter.
Interval: If you set the interval to be three days, the event runs three days after the day the Distributor re-reads eDirectory, then run every three days thereafter.
Weekly, Monthly, or Yearly: The event runs the first day, month, or specific date (the Yearly option) after the Distributor has re-read eDirectory. For example, on Wednesday you set up a Weekly event to happen each Sunday. The Distributor re-reads eDirectory on Thursday, so the event runs the following Sunday, and every Sunday thereafter.
Run Immediately: As soon as the Distributor is refreshed, the event runs, then runs thereafter according to the interval you set.

To cause an event for one of the interval-related schedule types to execute out of sequence (other than Run Immediately), you can use the ZfS Management role in iManager. For more information, see Novell iManager.

Repeating Actions

For schedule types that have the Repeat the Action Every field, how this option works depends on other factors, such as other schedules and how often the Distributor re-reads eDirectory.

For example:

You select Daily as the Send schedule for a Channel
You set 1:00 a.m. to midnight (23 hours) as the sending window
You set the Repeat the Action Every field with 1 hour as the repeat value

The action (sending the Distribution) will repeat as follows:

Starting at 1:00 a.m. and repeating every hour, the Distributor will queue the Distribution to be sent.
If a Distribution is in the process of being sent, it will continue to be sent.
Once a Distribution is off the queue after being sent, the Distributor will queue the next newer version for sending.
If a previously queued version of this Distribution has not been sent yet, the next newest version will be placed in the queue. In other words, only one version of the Distribution (the last built) will be queued while another version of the Distribution is being sent. The Distributor always sends the latest Distribution, even if the Subscriber already has it.