Previous Topic: Interlinked DependenciesNext Topic: Cross-Application Dependencies


Manual Dependencies

After a job runs, a manual task may need to be performed before the job's successor can run. To represent a manual task, you can set up a task workload object in your Application. A task represents work, such as a manual process that needs to complete before a subsequent job can run. A task does not run on a specific operating system. You must complete a task for its successors to become eligible for submission.

Example: Dependency of a Job on a Manual Task

Suppose that a UNIX job (J1) executes a script to produce a report that you must manually check. To represent the manual checking of the report, you can use a task (CHECKRPT.J). After you check the report, you would mark that task complete, and the server would release the successor job (J2).

The following illustration displays the dependencies between the jobs using a manual task:

The diagram shows how to set up a manual dependency between jobs using a task.

More information:

Create a Task