Controlling Execution Order Using Job Sets

You can control the order for a specified set of jobs when you want jobs that depend on other jobs to execute only if the jobs on which they depend have been successfully executed.

The first task is to define a job set, provided you have saved a parameter set for each of the jobs in the job set. Navigate to Admin, PSUB/Reports Jobs, then Job Sets and enter a name for the job set, which is restricted to alphabetic characters. List the various jobs in this set; the parameter set names previously saved are entered automatically or from a LOV. The Task Name field is typically the name of a report and is entered when the parameter set is entered.

For each job in the job set, enter the job label of a related job in the appropriate status column. The status column you choose indicates what status the job in the left-hand column should have before the related job should start. If you leave one of the fields blank and the job in the left-hand column ends with the corresponding status (for example, the job ends successfully and the field in the Success column is empty), the execution of the whole job set stops.

The Time-out field that refers to the job in the left-hand column has a default of 720 minutes. The Time-out field that refers to the related job indicates only whether the job is permitted to time out before or after another job executes.

If any of the jobs in a job set exits with a status of SUBMIT_FAILED or STOPPED, the whole job set aborts with a status of FAILURE.

Oracle Clinical limits you to a maximum of 52 saved records in a job set. If you run a sequence of more than 52 jobs, divide them into smaller sets.

You submit job sets following the menu path Admin, PSUB/Reports Jobs, then Submit Job Set and then providing a job set name, for which there is a list of values.

For more information, see:

• Log Files for Job Sets
  

Log Files for Job Sets

Oracle Clinical stores log files for job set submissions in the Report Queue Manager, and does not produce output files. For more information about seeing these log files, see Reports Queue Manager.