Purpose |
To create and maintain a schedule for a standing request by specifying the frequency with which the request should run in a nominated period |
|
Subsystem |
||
Structure |
Three Blocks |
Standing Request Period Standing Request Frequency ( Calendar Type/Date Alias) |
Standing Request Period |
Explanation |
NOTE: There are two methods of specifying when a job should run. This form is used to set up a schedule for standing requests. Use the form Maintain Request Schedule (JBSF5212) for all other requests. |
As part of defining a standing request, it is necessary to set up a schedule detailing the frequency with which the request should run. The system organises for the job(s) comprising the request to run at the intervals specified in this form. Security restrictions may limit the use of standing requests to specific system users. The form is accessed via the Standing Request Frequency navigation button on the central request form, Maintain Request Details ( JBSF5210). This button is displayed whenever the Standing Request indicator is set and saved. The indicator label is greyed out if a user is not permitted to create or alter a standing request, though the form can still be accessed for information.A diagram illustrates the steps to set up a request as a standing requestMuch of this block is for information only. It displays request context details carried from the central request form, including access to a pop-up window to see the intervals (set of times) assigned to the request's run window. The date fields in the block are used to enter the period (which can be open-ended) during which the standing request is current. |
Example |
Details of request number 67, created in the Maintain Request Details form, are shown in this block. Request number 67 contains a job to obtain and print statistics for study units, which are required on a regular basis during teaching weeks. The standing request period is set from 16th February 98 to 31st October 98. |
To view the intervals for the request's run window, using the Maintain Standing Request Frequency form: |
|
|
Rules:
|
To enter the period during which the given standing request is current, using the Maintain Standing Request Frequency form: |
|
In Insert mode:
Enter a date by keying directly in the field, or by using the calendar icon and selecting a date using the electronic calendar. Select a date using the date alias icon to access the Inquire On Date Alias Instance form (CALF7510). Follow instructions given for that form. On return to this block, the system inserts the selected date in the Alias Instance field.
|
Rules:
|
To modify the period during which the given standing request is current, using the Maintain Standing Request Frequency form: |
|
|
|
To remove the dates signifying the standing request period, using the Maintain Standing Request Frequency form: |
|
|
Rules:
|
Standing Request Frequency |
Explanation |
Records in this block specify the frequency with which a standing request will run during the standing request period. This can be entered as a day or days (for example, each Wednesday and Friday in February, April and June) or a day of the month (for example, the 18th of each month). Records here and in the next block (frequency using a date alias) can be set up in combination. |
Example |
The statistics for study units produced by the job in request 67 (detailed in the block above) are required every Friday morning during teaching weeks, so a staff member sets up the request to run each Thursday evening. This is achieved by selecting THU in the Day/s or Day of Month field of this block, and the months FEB, MAR, APR, MAY, AUG, SEP, OCT in the Months field. The Year is entered as 1998, and the time as 20:00. To add an extra two Thursdays required in July, two further record are created, one for 23 July, and one for 30 July. From 16th February, which is the start of the standing request period, the request will run each Thursday evening until 31 October, except for Thursdays occurring in June and in the first three weeks of July. |
|
Rules:
|
To modify a frequency record using the Maintain Standing Request Frequency form: |
|
|
|
To delete a frequency record using the Maintain Standing Request Frequency form: |
|
|
Standing Request Frequency (Calendar Type/Date Alias) |
Explanation |
Either as an alternative, or in combination with the Standing Request Frequency block, this block allows the entry of date aliases to determine the frequency with which standing requests will run during the standing request period.Standing request schedules which rely on date aliases must be considered in conjunction with setting up date alias instances for the same calendar type. Since the system attempts to re-schedule a standing request immediately after each scheduled date and time of running, a further date alias instance must exist at that time, or the request will be deemed to have completed.If, after a request has been submitted or re-scheduled to run (request status WAIT), a date alias instance is amended or added so as to fall before the request is due to run, this instance will be ignored. This is because the next run date is determined at the time the request status is set to WAIT. For an overview of processes corresponding to request statuses, see the section Checking on the Progress of a Request in the subsystem introduction. |
Example |
Building on the example used in the previous blocks, assume that statistics for study units are also required on government census dates. This requirement is built into the standing request by specifying CENSUS as the date alias in this block. The job will run on each census date within the standing request period, as well as at times scheduled in the previous block. |
Using a date alias to specify the frequency of a given standing request, using the Maintain Standing Request Frequency form: |
|
In Insert mode:
|
Rules:
|
To modify a date alias frequency record using the Maintain Standing Request Frequency form: |
|
|
|
To delete a date alias frequency record using the Maintain Standing Request Frequency form: |
|
|
Changes within this form will have the following notable effects: |
|
Last Modified on 30 September 1999