Purpose |
To allow the specification of 'windows' of time within which scheduled jobs may start, and to record any run mode restrictions against these windows |
|
Subsystem |
||
Structure |
Two Blocks + overlay |
Run Window Run Window Run Mode Restriction (overlay block) |
Navigation Button invokes: |
Run Window Run Mode Restriction block (overlay) |
|
Run Window |
Explanation |
Run windows identify sets of times within a week. They provide a mechanism to control when jobs run because a run window must be specified in a request to run batch jobs, and may be specified against individual jobs, whether run in batch or immediate mode. Jobs can start only during their specified run window, and only if there is an active batch queue which can operate in the same run window. Basic run windows details are created and maintained in this block. The periods during which each run window is in effect are recorded in the Run Window Interval block below. It is also possible to restrict a run window to a particular mode of running. This is done by accessing the Run Window Run Mode Restriction block via the navigation button. |
Example |
The week could be set up with a run window for business hours, another for jobs run after hours, and a third for weekend work. |
To create a new run window record using the Maintain Run Windows form: |
|
|
|
To modify a run window record using the Maintain Run Windows form: |
|
|
Rules:
|
To delete a run window record using the Maintain Run Windows form: |
|
|
Rules:
|
Run Window Interval |
||||
Explanation |
||||
This block is used to record, for each run window in the Run Window block, the periods within a week which constitute that window. |
||||
Example |
||||
Run Window |
Start Day of Week |
Start Time |
End Day of Week |
End Time |
AFT-HOURS |
MONDAY |
18:01 |
TUESDAY |
07:59 |
WEEKEND |
FRIDAY |
00.00 |
SUNDAY |
23:59 |
To create a new run window interval record using the Maintain Run Windows form: |
|
|
Rules:
|
To modify a run window interval record using the Maintain Run Windows form: |
|
|
|
To delete a run window interval record using the Maintain Run Windows form: |
|
|
Run Window Run Mode Restriction |
Explanation |
There are two system defined run modes, IMMEDIATE and BATCH. If desired, particular run windows can be specified as running in one mode only, which enables a broad level of management of how (and therefore when) jobs can run. Batch jobs in requests have to start within a run window specified for the request. It is possible to restrict the number of jobs that can be run concurrently in a run window in BATCH run mode. For example, if the maximum for concurrent jobs is set to 3, for example, and there are 5 active batch queues for the same run window available, only 3 queues can be used at the same time to execute jobs in the run window. This block, which is displayed as an overlay when the Run Mode Restrictions navigation button is selected, allows for these restrictions to be applied to a run window. If there are no entries in this block for a particular run window, then
|
Example |
At certain times of year (for instance, during the enrolment period) it may be desirable to prevent users from initiating runtime reports so as to reserve processing power for online database access. This could be achieved by restricting the business hours run window to BATCH run mode. Another use might be to influence the proportion of processing power allocated to batch jobs during the day by recording both modes against the run window, but setting a maximum for concurrent jobs against the BATCH mode. |
To place a run mode restriction on a run window, using the Maintain Run Windows form: |
|
|
|
To modify a run window run mode restriction record using the Maintain Run Windows form: |
|
|
|
To delete a run window run mode restriction record using the Maintain Run Windows form: |
|
|
Last Modified on 30 September 1999