JBSF5300 - Maintain Request Job Run

Purpose

To monitor the running of Job Requests and review outcomes

SubSystem

Job Control & Scheduling

Normally Run By Job Control Specialist
Anticipated Frequency As required
Structure Block Job Run
Buttons Job Output (Overlay)
Job Parameters (GENJ0010)
Cancel Job
Refresh
Order By (pop-up window)
Run Log (JBSF5301)
Job Diagnostics (pop-up window)
Request Job Notification (JBSF5213)

  

Job Run Block

This form is used to inquire on the progress of a job or jobs once a request has been submitted to run. If accessed from the Main Menu, or the Maintain Request Details form (JBSF5210) by selecting the Job Run Button, or from a Report or Job Parameter form, context information is carried forward.

The form also allows review of the outcome of recent Job Runs, using Query Mode. Query criteria can be entered in any field to refine the inquiry, and the list of jobs can be re-ordered using the Order By pop-up window. A Spread table allows access to the fields at the far right.

It is also possible to use this form to cancel individual jobs that have not yet started running.

An alert message will be displayed when the user attempts to cancel a job that is not a Staff Connect Report.

Information about the meaning of the request and Job Run statuses is given in Checking on the Progress of a Request in the Subsystem introduction.

For example, a job in request 35 has been carried forward as the context record displayed in this form:

Field Name Data in field Interpretation
REQUEST NUMBER 35 This job is included in request 35
JOB NAME CALR0620  
JOB NUM 2 This is the number assigned to the job within request 35. If the Sequence indicator was set, the job will have run second in sequence within the request.
Job Run STATUS COMPLETE The job completed successfully
QUEUE ID 3 It ran in batch queue 3
SCHEDULED DATE & TIME 23/09/2003 18:15 It was scheduled to run on 23rd September 1998 at 6.15 p.m.
START DATE & TIME 23/09/2003 18:18:35 It actually started to execute 3 minutes and 35 seconds later
FINISH DATE & TIME 23/09/2003 18:20:46 It completed 2 minutes and 11 seconds after starting
CPU TIME 00:00:01 To run this job, the computer allocated approximately 1 second of its time in total

Buttons

Job Output (overlay)

The Job Output button displays an overlay (Job Output Destination) that provides details of the destination to which any output from the selected report or job is sent. The button is only active where a job or report produces physical output. The Re-send Output button within the overlay allows for previously sent outputs to be resent to the original destination or redirected to a new destination.

Job Parameters (GENJ0010)

The Job Parameter button invokes the parameter form for the selected job or report and displays the Parameters that were used for that particular job/report run. Parameters cannot be changed at this stage.

Cancel Job

Displays an Alert Message if the user attempts to cancel a job: "Are you sure that you wish to cancel this job?" If there is no Staff Connect functionality, and the job is not a Staff Connect job, but is running, the message will read, "This job cannot be cancelled while RUNNING". If Staff Connect functions are available, the Cancel button will automatically cancel a Staff Connect Report Request when selected.

Refresh

The Refresh button performs a re-query within this form using the previously used query criteria. This updates the displayed data, particularly the Job Run Status, and is used to monitor the progress of jobs and reports.

Order By (pop-up window)

The Order By button invokes a pop-up window which is used to change the order in which job records are listed on this form. Changing the order has no effect on when the jobs will run.

The records can be ordered by the following fields:

  • Scheduled Date & Time (in order from most recent to oldest)
  • Request Number
  • Queue ID
  • Start Date & Time (in order from most recent to oldest)
  • Finish Date & Time (in order from most recent to oldest)

When the order is changed, the new sequence takes effect on re-query. The ordering facility can be used in conjunction with query criteria to refine the way in which information about jobs is presented.

For example, the list is ordered by request number within scheduled date and time. Assume that five requests (Request Numbers 34, 35, 36, 38, 42) were all scheduled to run on 22 October at 1 a.m. Request 36 has three request jobs - FINJ3500 was run three times, with different parameters each time.

Request Number Job Name Queue ID Scheduled Date & Time
34 SECR0044 2 22/10/03 01:00
35 CALR0630 3 22/10/03 01:00
36 FINJ3500 1 22/10/03 01:00
36 FINJ3500 2 22/10/03 01:00
36 FINJ3500 2 22/10/03 01:00
38 CRSR0610 4 22/10/03 01:00
42 ORGR0220 2 22/10/03 01:00
30 XXXX1111 1 21/10/03 23:00

The order is changed to scheduled Date and Time within Queue ID. When next re-queried, this is the sequence:

36 FINJ3500 1 22/10/03 01:00
30 XXXX1111 1 21/10/03 23:00
34 SECR0044 2 22/10/03 01:00
36 FINJ3500 2 22/10/03 01:00
36 FINJ3500 2 22/10/03 01:00
42 ORGR0220 2 22/10/03 01:00
35 CALR0630 3 22/10/03 01:00
38 CRSR0610 4 22/10/03 01:00

Job Diagnostics (pop-up window)

The Job Diagnostics button invokes a pop up window which displays diagnostic information for the selected request.

Request Job Notification (JBSF5213)

The Request Job Notification button opens the JBSF5213 form in which contact details are displayed and maintained.

 

The Job Run block contains:

  • Request Number
  • Job Name
  • Job Num

Spread Table

  • Job Run Status
  • Queue ID
  • Scheduled Date and Time
  • Start Date and Time
  • Finish Date and Time
  • Elapsed Time
  • Standing Request check box
  • Schedule ASAP check box
  • Requested By Person ID
  • Person Name
  • Oracle User Name

Buttons

    • Job Ouput (Overlay)
      • Output
      • Printer
      • Copies
      • Email
      • Re-send Options button
      • Back button
    • Job Parameters (GENJ0010)
    • Cancel Job
    • Refresh
    • Order By (Pop-up window)
      • Order By
      • Clear button
      • Back button
    • Run Log (JBSF5301)
    • Job Diagnostics (Pop-up window)
      • Request Number
      • Job Name
      • Job Run Status
      • Diagnostics
      • Back button
    • Request Job Notification ( JBSF5213)

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 Procedure DBMS_JOB on the database for the Job Scheduler Automatically Cancels Connect Jobs when the Time Limit is defined to the Run Window and the job has been running is in excess of that limit. See JBSF4410 for further details.

Note: The DBMS_JOB Procedure is set to run at intervals on the database. What interval is set will depend on when a running job is automatically cancelled. For example;Time Limit on Run Window set to 00:30 minutes – DBMS_JOB procedure run interval set to run every 00:30 minutes, on the hours – Job is scheduled to run at 1 minute past the hour – at 00:30 minutes past the hour, Job has only being running for 00:29 minutes – Job is not Cancelled due to not being in excess of the Run Window Time Limit – on the hour, DBMS_JOB runs and Automatically Cancels Job. Job has been running 00:59 minutes instead of it’s Run Window, Time Limit of 00:30 minutes.

The Job Diagnostics button opens a pop-up screen to display the state of the job request. This button is only enabled when the selected job request has a status of WAIT or SCHEDULED.

The Request Job Notification button opens the form JBSF5213, in which contact details can be recorded for appropriate persons to receive email/sms notification when the status of this job or report has changed. This button is disabled if the user does not have access to JBSF5213.

A list of available messages for the Job Diagnostics pop-up window is shown below

Message Number Message TEXT
1774
The batch queue is not within the run window for the job.
1775
The jobs within the request must be run sequentially, jobs exist that must run before this job can run.
1777
The job is dependant on another job within the request which has not completed successfully.
2072
The jobs within the request must be run in priority order, jobs exist that must run before this job can run.
4900
Job delayed as a conflicting job is now running.
12471
The schedule time has not been reached.
12472
The application server may be down or the URL could be incorrect.
12473
Oracle server error, please consult your system administrator
12474
All batch queues are inactive.
12475
The Maximum number of jobs running for the run mode and run window has been reached.
12476
The job is not able to run against the available batch queue due to an application server restriction existing for the job type.
12474
The job is not able to run against the available batch queue due to an application server restriction existing for the job.
12478
The job is not able to run against the available batch queue due to a batch queue priority restriction existing for the job.
12485
The current date and time is not within the scheduled run window for this job.

 

To inquire on the progress of Job Requests, and view outcomes, using the Maintain Request Job Run form:
  • Enter query details in the appropriate fields
  • Execute the query
  • If the job has a status of WAIT or SCHEDULED, further information about the current state of the request may be available via the Job Diagnostics button

Rules/Notes:

The list of values can be used to select a query criterion in the Job Run Status field.

Job Run statuses are: WAIT, SCHEDULED, RUNNING, COMPLETE, FAILED, ABORTED, CANCELLED.

Jobs will revert to WAIT status after executing if they are scheduled to run again within the request.

Jobs submitted using the Schedule ASAP button will have an initial status of SCHEDULED.

To Cancel a Job waiting to run using the Maintain Request Job Run form:
  • Place the cursor in the Job Run Status field of the record to be cancelled (or access the list of values for this field in the correct record)
  • Select CANCELLED from the list displayed
  • Save.  OR
  • Select the job to be cancelled
  • Select the Cancel Job button
  • Save

Rules/Notes:

Jobs can only be cancelled if they have a status of WAIT, SCHEDULED or RUNNING (Running can only be cancelled if institution has Staff Connect functionality).

If all jobs in a request have been cancelled, and there are no more scheduled times to run, the request itself needs to be cancelled in the central form Maintain Request Details (JBSF5210).

If using the Cancel button, the outcome will be determined by whether or not Staff Connect functionality is available. See the Cancel Button description above for details.

To Re-order the sequence in which jobs are listed on the Maintain Request Job Run form:
  • Select the Order By button
  • Optionally, to remove field names from all the Order By fields, use the Clear button
  • For each position required in the ordering hierarchy, click on an 'Order By' field or corresponding arrow and select a field name from the drop-down list
  • Return to the main form by using the Back button. The new order takes effect next time a query is executed

Rules/Notes:

Re-ordering works as in this example:

Selecting 'Queue ID' in the top Order By field, 'Request Number' in the next field down results in job records being presented, first grouped by batch queue and then, in ascending request number order within batch queue. Selecting the 'space' at the bottom of the drop-down list clears an Order By field.

 

Last Modified on 15 March, 2006