3.1.2 Building a jobnet

The jobnet definition flow for automating applications in JP1/AJS3 is as follows:

1. Create a job group as required.

2. Create a jobnet.

3. Create the jobs.

4. Sequence the created jobs as required.

5. Set a start condition for the jobnet as required.

For details on setting a start condition, see 3.4 Defining a start condition.

In JP1/AJS3, operations such as scheduling, execution, and management are performed in application units, that is, by root jobnet. For this reason, the jobnets will be easier to manage as a whole if you have some criteria in mind when grouping processes into jobnets.

Below, we provide some examples of jobnet creation to illustrate how to group processes into a jobnet.

• Example of management by application category

  This example builds a jobnet of related applications. An application-based jobnet allows jobs to be easily added, changed, or deleted whenever required.

  The following figure shows an example of management by application category.

  Figure 3‒14: Example of management by application category

• Example of management by department

  This example builds a jobnet categorized by department. A departmental jobnet facilitates overall jobnet management and prevents operators in other departments from accessing the wrong applications.

  The following figure shows an example of management by department.

  Figure 3‒15: Example of management by department

• Example of management by processing category

  This example builds a jobnet by processing unit. With a processing-based jobnet, there is no need for complex scheduling or structuring into hierarchical levels.

  The following figure shows an example of management by processing category.

  Figure 3‒16: Example of management by processing category

If you are using commands to operate on jobnets, it would be best to use lower-case alphanumeric characters when setting names to allow for the use of regular expressions.

To Page Top