Purpose |
To allow the creation of interdependent relationships between system jobs |
|
Subsystem |
Job Control and Scheduling |
|
Structure |
Three Blocks |
System Job |
Image |
It is anticipated that the data in this form will be set up and maintained by IT staff. The second of the three blocks - System Job - displays the context record. There are zoom buttons ( , ) in the first and third blocks corresponding to each record displayed in these blocks. These buttons permit the adjacent record to be dropped or elevated into the middle block, where it in turn becomes the context record with its related records displayed in the other two blocks.Spread tables allows job details to be seen in all three blocks. |
System Job |
Explanation |
This is the context record which, if this form is accessed from Maintain Job Details (JBSF4110), is carried from that form. It is possible to re-query on any job. If interdependent jobs are included in the same request, prerequisite jobs must complete successfully before dependent jobs can run. In terms of this form, jobs specified in the Prerequisite Job block must run before the job in the System Job block, which in turn must run successfully before any jobs specified in the Dependent Job block can run. |
To inquire on the dependency relationships for a job other than that initially displayed, using the Maintain Job Dependencies form: |
|
|
Prerequisite Job |
Explanation |
This block holds all jobs defined as prerequisites of the job shown in the context block. New jobs can be linked by adding them in this block, and existing dependency links removed by deleting the jobs. Where the mandatory indicator is set for a prerequisite or dependent job, that job must be included in any request which includes the job shown as the system job, and vice versa. If this indicator is not set, the jobs can exist as 'stand alone' in a request, but if both are included in the same request, prerequisite jobs must run before dependent jobs. If a prerequisite job fails in a request, dependent jobs will have their status set to ABORTED and will not run. |
To create a new prerequisite relationship to the system job, using the Maintain Job Dependencies form: |
|
|
|
To remove the link between a prerequisite job and context job, using the Maintain Job Dependencies form: |
|
|
Dependent Job |
Explanation |
This block holds all jobs defined as dependents of the job shown in the context block. New jobs can be linked by adding them in this block, and existing dependency links removed by deleting the jobs. Where the mandatory indicator is set for a dependent job, that job must be included in any request which includes the job shown as the system job, and vice versa. If this indicator is not set, the jobs can exist as 'stand alone' jobs in a request, but if both are included in the same request, prerequisite jobs must run before dependent jobs. |
To create a new dependent relationship to the system job, using the Maintain Job Dependencies form: |
|
|
|
To remove the link between dependent job and context job, using the Maintain Job Dependencies form: |
|
|
Changes within this form will have the following notable effects: |
Creating a new dependency relationship may prevent existing waiting requests from running if
|
Last Modified on 30 September 1999