Top of JBS | Index | Table of Contents | Feedback |
JBSF5210 - Maintain Request Details
Purpose |
To allow the creation, maintenance, submission and querying of Job Requests, and as an access point to all other forms and processes concerned with Job Requests. |
|
Subsystem |
Job Control and Scheduling |
|
Normally Run By | Job Control Specialist | |
Anticipated Frequency | As required | |
Structure | Blocks | Request |
Request Job | ||
Buttons | Submit Request | |
Cancel Request | ||
Request Schedule (JBSF5212) or Standing Request Schedule (JBSF5211) | ||
Request Job Notification (JBSF5213) | ||
Job Parameters (STAJ0110) | ||
Job Output (JBSF5230) | ||
Job Run (JBSF5300) |
Request block Note: If a job is to be run immediately or is scheduled to run as soon as possible, rather than in batch mode, this form is not used. Refer to Running a Report Immediately in the Subsystem Introduction. Job Requests are the means by which users initiate batch jobs, previously defined within the Callista System, to run reports, update the database and perform System maintenance tasks. A set of interconnected forms is used to perform the tasks necessary to create, modify and query Job Requests, and to track the progress of jobs once a request has been submitted. This form, Maintain Request Details, is the central form of the set, and contains buttons to the associated forms, and function buttons to initiate processes. This Request block, and the block below which is used to specify the job(s) composing the request, contain the core information about the request. A configurable button in this block goes either to the Maintain Request Schedule Details form (JBSF5212), or the Maintain Standing Request Frequency form (JBSF5211) to set up a schedule for running the request. When this form is accessed directly from a job/report parameter form, data is defaulted into the form. The Run Window can be changed and jobs can be added or deleted. If the person requesting this job has default Job Notification details recorded in SECF0066, then appropriate sma and/or email messages will be sent to this person. Job Notification details for this request can be viewed and modified in JBSF5213, accessed by clicking on the Request Job Notification button. It is possible to create new requests by using an existing request as a template. This section links to the documentation for interconnected forms at appropriate points. A complete overview of the Subsystem is given in Understanding Job Control and Scheduling, including an outline of all the forms needed to create and submit a request, in the section Steps in a Job Request. A reminder: It is necessary to save after selecting the function buttons Cancel Request, Submit Request and Re-plan Request in this block. Request Job block The job or jobs to include in a request are specified in this block. There are various attributes of jobs that determine whether they can form part of a particular request, and how they must be requested. These factors apply:
Including Jobs in a Request Priority. Some users are permitted, for designated jobs, to override the Priority assigned to those jobs. Once Job Records are saved, it is possible to alter the sequence in which jobs are to run, as an alternative to their running in Priority Order. Parameters and Output. Jobs usually require parameter values to be entered by the user. They may also need output destination details specified at this stage, if destination defaults have not been assigned. For each job, therefore, it may be necessary to access:
Entry order. When recording several jobs for a request, the user has a choice about the order in which tasks are done. It is possible:
The instructions given in the next table are for the first method. Priorities can be changed (if permitted) at any time, and the sequence can be amended at any point after all jobs are saved. Job tracking. Once a request has been submitted, the Job Run button gives access to the Maintain Request Job Run form (JBSF5300). Use this form to track the progress of individual jobs. An example of the complete request process is given in the Subsystem Introduction. |
The Request block contains:
The Request Job block contains: |
Rules/Notes: When a job is a Callista Connect Report (when an institution has Connect), the Job Parameter button will be disabled. This can be identified by having the Parameter field set to SCPARAM. The Request Job Notification button will be disabled if the user does not have access to JBSF5213. The Job Parameter button invokes the Parameter form for the selected job, displaying the parameters that were used for that particular job. Parameters cannot be changed at this stage. |
To create a new Job Request using the Maintain Request Details form: In Insert mode:
Access the appropriate form and follow the instructions given in that form's documentation.
|
Rules/Notes: Note that steps 3 to 7 can be performed in a different order, as required. This may necessitate saving data before performing the next step. The ID of the person making the request is inserted automatically by the system. Values in the Request Status field are maintained by the System. For a new request, the status defaults to PLANNED.The System inserts a unique request number when the request is saved. The Abort On Error check box is relevant where several jobs are specified for a request. It is set as the default, and indicates that subsequent jobs are not to be run (but are to be 'aborted'), if a previous job fails to complete successfully.The Sequence check box, if set, indicates that jobs in a request are to be run in sequence rather than in Priority Order. The required sequence is organised in the Request Job block. This facility is useful when it is not permitted to override the priorities set. Jobs within a request will never be run concurrently, even if there are several batch queues open.The Standing Request check box, if set, marks the request as one to be scheduled and run automatically by the System at pre-determined intervals. The right hand button in the block is then configured to access the correct Schedule form. The check box label is greyed out if you are not permitted to run Standing Requests. Security restrictions may prevent some users from creating Standing Requests. To check, use the Zoom to go to the Maintain Person Preferences form (SECF0066), where a check mark in the Allow Standing Request check box indicates permission.To successfully submit a request, there must be at least one future Date/Time in the schedule at the time the request is submitted. If the person requesting this job has Job Notification details recorded in SECF0066, then appropriate messages will be sent to this person. |
To inquire on existing Job Requests using the Maintain Request Details form: In Query mode:
(Inquire on the progress of individual jobs via the Run Job button in the Request Job block.) |
Rules/Notes: A
request can have the following Status Values: A submitted request's Status is updated automatically by the System as the request is processed, but it is necessary to re-query to see the current status in the Request Status field. Hint: Using the three keystrokes F7, F7, F8 is a quick way to re-query the last record accessed. |
To duplicate an existing request, as the basis for a new request, using the Maintain Request Details form:
|
Rules/Notes: Hint: The function key F6 is a quick way to create a new record, and F4 duplicates the record selected previously. |
To
modify Job Request details in this block, before submission, using the
Maintain Request Details form:
|
Rules/Notes: The modification of individual jobs in a request is undertaken in and from the Request Job block. Request schedules are modified either in the Maintain Request Schedule Details form (JBSF5212) or the Maintain Standing Request Frequency form (JBSF5211). |
To
modify a Job Request, after submission, using the Maintain Request Details
form:
|
Rules/Notes: Requests that have been submitted, and have a status of WAIT, can be re-set to PLANNED Status, and modified. Once a request becomes SCHEDULED, this is no longer possible. |
To
cancel a Job Request using the Maintain Request Details form:
|
Rules/Notes: A saved request cannot be deleted. |
To specify a job as part of a request, using the Maintain Request Details form: In Insert mode:
|
Rules/Notes: If the form has been accessed from a report name or other job name on a menu, the job selected there is displayed when this block is entered. This record must still be saved. (Continue from step 2). If the form is entered from a job/report parameter form, the job/report details are displayed when the form opens. A request can include more than one job.The same job may be included more than once in a request. The list of values shows open jobs only. A job may have more than one output, and for each output, one or more destination sets. Refer to Output from Jobs in the introduction, for an outline of possible output combinations. |
To
alter the run sequence of jobs in a request, using the Maintain Request
Details form:
|
|
To
modify job details for a request using the Maintain Request Details form:
|
Rules/Notes: Jobs details can only be amended while the request has a status of PLANNED. A Job Record (as designated in the Job Name field) cannot be changed, once saved, it can only be deleted. Its priority can be amended if permitted by the user's security access. Parameter and output details can be amended. |
To delete a job from a request using the Maintain Request Details form:
|
Rules/Notes: Jobs can only be deleted while the request has a status of PLANNED, and as long as it has not already been submitted once (i.e. is not a 're-plan'). |
Last modified on 10 November, 2010 11:40 AM
History Information
Release Version | Project | Change to Document |
12.0.0.3 | 1646 - Skills VIC VET FEE-HELP Reporting | Added note re: job parameters button. |