3.1.4 Creating a job flow

A job flow is easy to create in the Jobnet Editor window of JP1/AJS3 - View.

In the Jobnet Editor window, you can easily create a job flow simply by linking jobs with arrows called relations. For details on JP1/AJS3 - View operations, see 5. Defining Jobnets in the Job Management Partner 1/Automatic Job Management System 3 Operator's Guide.

Figure 3‒16: Example of creating a job flow in the Jobnet Editor window

A variety of job flows can be created, depending on how the jobs are sequenced and inter-related. Some examples of job flow creation are provided below.

Organization of this subsection

(1) Single processing path
(2) Multiple processing paths
(3) Nested jobnet
(4) Sequencing jobs in different jobnets

(1) Single processing path

Job 1, Job 2, and Job 3 are executed sequentially in a single processing path. The job flow is created as follows:

Figure 3‒17: Job flow in a single path

To Page Top

(2) Multiple processing paths

The following figure shows an example of creating a job flow in multiple processing paths.

Figure 3‒18: Job flow in multiple paths

When Job A is executed, the processing branches into two paths: Job A -- Job B -- Job C, and Job A -- Job D -- Job E.

To Page Top

(3) Nested jobnet

You can use nested jobnets in a job flow. Examples of using nested jobnets are shown below.

Nesting a jobnet

The following figure shows an example of nesting a jobnet within the job flow.

Figure 3‒19: Example of using nesting a jobnet

When Job A completes execution, the jobs defined in Jobnet 1 are executed. When processing of Jobnet 1 is finished, Job B is executed.

Grouping multiple jobs

The following figure shows an example of grouping multiple jobs into nested jobnets.

Figure 3‒20: Example of grouping multiple jobs into nested jobnets

Joining two paths

Using a nested jobnet, you can join two processing paths into a single path.

The following figure shows an example of joining the paths Daily process 1 -- Daily process 2, and Daily process 1 -- Monthly process -- Daily process 2, into one flow.

Figure 3‒21: Joining jobnets into one flow

Because the two daily processes are executed every day and the monthly process is executed only once a month, JP1/AJS3 will skip any jobnet not scheduled for a particular day. This means that the two paths can be joined into one path.

To Page Top

(4) Sequencing jobs in different jobnets

In JP1/AJS3, you cannot use relation lines to sequence jobs among different jobnets. If you want to sequence jobs among jobnets, create a job flow by using one of the following methods:

Split a jobnet
Integrate jobnets
Use jobnet connectors

For details about jobnet connectors, see 2.2.4 Using jobnet connectors to control the order of root jobnet execution in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.
Use wait conditions

For details about wait conditions, see 2.2.5 Using wait conditions to control the order of unit execution in the Job Management Partner 1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

The following figure shows examples of sequencing jobs among different jobnets.

Figure 3‒22: Examples of sequencing jobs among different jobnets

[Figure]

To Page Top