6. If you use All requests, you can set the Skip field so that the product generator does
not process every occurrence of the associated task.
By default, an All request causes data from every task to be processed. The Skip time
breaks the day into equal time intervals starting from midnight.
A product is generated, at most, once for each skip time interval. The first occurrence of
data from the associated task is used for each interval.
For example, a Skip time of 00:15 (15 minutes) means that the product is generated
no more frequently than every 15 minutes, regardless of how often the associated task
runs.
In the following figure, the Skip field for an All request is set so that there are 2
occurrences of the task in each interval. Only the first occurrence is used to generate
the product.
TASK TASK TASK TASK TASK TASK TASK TASK
Time
Product Product Product Product
Skip Time
Interval
The default value of the Skip field is 00:00, indicating no tasks are skipped.
When the Master Schedule is displayed, a change in the Skip Time is applied to all of
the sites.
You must consider the task schedule when specifying the Skip time.
During operation, the Next-Data-Time field changes to show the next possible time
that the product can be generated. This depends on the Skip time and the request (All
or Next) as follows:
Skip and Request Values
Description
Next Any Skip Time After completing a Next request, the Next-Data-Time field is reset to
the data time (plus 1 second) of the task that was just processed.
This means that issuing another Next request processes the next
occurrence of the associated task.
The Skip time is ignored.
All Skip Time = 00:00 The product is generated for every occurrence of the associated task.
The Next-Data-Time field is reset to the data time (plus 1 second) of the
task that was just processed (identical to the Next request case).
This is the same as issuing a series of Next requests.
Chapter 4 – Scheduling Products
RESTRICTED 117
To Next Page
Loading...