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

Job Control & Scheduling

Run Window Block

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 button.

For 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.

The Time Limit field is only available for institutions with Staff Connect function.

Run Window Interval Block

This block is used to record, for each Run Window in the Run Window block, the periods within a week which constitute that window.

Button - Run Mode Restriction

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, 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 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

• Both immediate and batch jobs can be run during the intervals when the window applies
• The full number of available batch queues can be used concurrently by jobs in the window, subject to other considerations such as batch queue priority restrictions.

For example, at certain times of the 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.

Staff Connect Function

System Administrators can set up Time Limits for reports to be run through Staff Connect. The report will run until completion, or it is cancelled by the user, or the Auto Cancel fuction.

Warning

When attempting to run any job/report in immediate mode, and the result is shown in a web browser with 'pop-up' enabled, the job/report will not show. Disable 'pop-up' and try again. This applies to all pop-up programs (Google, IE XP SP2, etc).

See Staff Connect Information for further details on Forms and Jobs.

The Run Window block contains:

• Run Windows
• Description
• Time Limit
• Closed check box

  Button

  • Run Mode Restriction (overlay)
    • System Run Mode
    • Description
    • Maximum Concurrant Jobs
    • Back button

The Run Window Interval block contains:

• Start Day Of Week
• Start Time
• End Day Of Week
• End Time

Rules/Notes:

The Time Limit function provides System Administrators with the ability to set up time limits on reports that can be run via Callista Connect. The Time Limit indicates the elapsed time between when the report started to run and the current time. Users do not have the ability to specifically schedule requests; requests will be automatically scheduled on their behalf.

Note that the frequency set has an effect on the total running time of the job.

For example, if the report Run Windows Time Limit is set at 30 minutes, and the Cancellation Job Frequency is also set to every 30 minutes, then the maximum time that a report could possibly run before actually being cancelled will be 59 minutes.

• Enter Insert mode
• Enter the new Run Window name in the Run Window field of a blank record
• Enter the corresponding Description for the Run Window in the Description field
• If Staff Connect functionality, fill in the Time Limit using HH:mm format
• Use the Closed check box if this information is not to be changed
• Save

To modify a Run Window record using the Maintain Run Windows form:

• Find the record to be modified
• Modify the record as required
• Save

Rules/Notes:

A Run Window name cannot be modified. Only the Description and the value of the Closed check box may be changed.

To delete a Run Window record using the Maintain Run Windows form:

• Find the record to be deleted
• Locate the cursor in the record to be deleted
• Delete record
• Save

Rules/Notes:

A Run Window cannot be deleted if Run Window Interval records or Run Window Run Mode Restriction records exist for it. Neither can it be deleted if it is specified in a job request or a batch queue

A Run Window can be Closed, preventing its further use. Jobs that have already been saved in an existing request for that Run Window (request statuses PLANNED, WAIT or SCHEDULED) will not be prevented from running

• Enter Insert mode (for all but first record to be created)
• Select the day of the week on which the interval starts from the list of values (or key the first one or two letters) in the Start Day Of Week field of a blank record
• Key in the start time of the interval in the Start Time field
• Select the day of the week on which the interval ends from the list of values (or key the first one or two letters) in the End Day Of Week field
• Key in the end time of the interval in the End Time field.
• Repeat from 1 to create the required number of intervals. (Reminder: Function key F3 duplicates the field above.)
• Save

Rules/Notes:

The intervals for a single Run Window cannot overlap.

The System gives a warning if intervals for different Run Windows overlap.

An alternative to entering insert mode to create each subsequent record after the first is to click in the Start Time field of a blank record.

Clicking in a Day of Week field produces the pop-down list, but tabbing to the field allows keying.

The System uses the 24 hour clock (e.g. 5 p.m. should be entered as 17:00).

Time can be entered in a variety of formats. For example, 8:01 can be entered as 8.01, 8-01 or 8:1, amongst others.

An entered time like 8.3 is interpreted by the System as 8.03.

To modify a Run Window Interval record using the Maintain Run Windows form:

• Find the record to be modified
• Modify the record as required
• Save

To delete a Run Window Interval record using the Maintain Run Windows form:

• Find the record to be deleted
• Locate the cursor in the record to be deleted
• Delete record
• Save

• Access the overlay block using the Run Mode Restrictions button
• Enter Insert mode
• Select the Run Mode required from the list of values (or key a valid value) in the System Run Mode field of a blank record
• Optionally, enter a number in the Maximum Concurrent Jobs field.
• Save
• To reinstate previous screen configuration, select Back

To modify a Run Mode Restriction record using the Maintain Run Windows form:

• Find the record to be modified
• Change the value in the Maximum Concurrent Jobs field
• Save

To delete a Run Mode Restriction record using the Maintain Run Windows form:

• Find the record to be deleted
• Locate the cursor in the record to be deleted
• Delete record
• Save