Purpose

The process is used to perform a bulk delete of Job Requests which, by virtue of their age and status, are deemed to be no longer required. Refer also to the Subsystem Specialist section.

SubSystem

Job Control & Scheduling

This job deletes the report output files and associated job details for all requests that haven’t been modified since the specified number of days have passed.

The job executes the database routine which does the following:

• Gets all the requests with a status of COMPLETED or CANCELLED that weren’t changed since the specified number of days passed as a parameter to the routine
• For each request retrieved in the step above, calls a table to delete the output files and the request details
• If the job is unable to delete a request, it continues on to the next request

If Staff Connect is available, the jobs that were run within Connect will also be deleted within the above parameters.

See Staff Connect Information for further details.

JBSJ9120 is used to delete obsolete Output files

The Delete Old Job Requests block contains:

Parameters

• Number of Days Since Request Modified

Rules/Notes:

No reports are produced. The Job Log shows the number of requests deleted by this job

This job is typically run:

• As a standing request in an off-peak run widow
• As frequently as the institution's data management regime requires

Rules/Notes:

The single parameter, Number of Days Since Request Modified, refers to the elapsed days between the Date when the status of the request last changed and the current Date.

Good practise would be to set this parameter to equal, or slightly exceed, the frequency with which this job is run by a standing request. For example, where this job is set to run monthly, set the parameter to 31 or 32.

Job Requests will only be deleted if there are no related extract records present.