Hitachi

JP1 Version 12 JP1/Automatic Job Management System 3 Overview


3.4.1 Purpose of a start condition

By setting a start condition, you can execute a jobnet when an event occurs, just like defining a preceding event job to trigger a jobnet.

The following figure shows how the system executes a jobnet that has a preset start condition.

Figure 3‒44: Execution of a jobnet with a start condition

[Figure]

As a start condition, you can only define an event that can be monitored by an event job. For example, you can define a JP1 event, incoming email, file update, or time interval.

You can define a start condition only for the root jobnet. Only one start condition can be set. When you set a start condition, the system creates a jobnet called .CONDITION, which monitors for the set condition to be satisfied. In the .CONDITION jobnet, you define an event job for monitoring the event that will act as the condition. For how to set a start condition, see 5.4 Setting a start condition in the JP1/Automatic Job Management System 3 Operator's Guide.

A start condition can consist of multiple event jobs. When you define multiple event jobs for the start condition, whether the condition is satisfied depends on which of the following you use:

AND and OR conditions are explained next.

AND condition

An AND condition is satisfied when all of the event jobs defined in the condition have occurred.

The following example shows how a jobnet is executed when a start condition, defined as an AND condition, is made up of a Monitoring files job and a Receive JP1 event job.

Figure 3‒45: Example of an AND start condition with multiple events

[Figure]

Cautionary note

To monitor multiple conditions by using an AND condition, make sure that same event does not occur in succession. In the example above, make sure that the file update events do not occur in succession.

Occurrence of a specific event in succession might generate a lot of jobnet generations that wait for other events combined by that specific event by the AND operator, which adversely affects performance.

For details about execution generations, see 3.4.2 Monitoring generation and execution generation.

OR condition

An OR condition is satisfied when one of the event jobs defined in the condition occurs.

The following example shows how a jobnet is executed when a start condition, defined as an OR condition, is made up of a Monitoring files job and a Receive JP1 event job.

Figure 3‒46: Example of an OR start condition with multiple events

[Figure]

When you use an OR condition, the condition is satisfied when either one of the defined events occurs.

When concurrent execution is enabled, multiple instances of the jobnet may run at the same time, executed each time the start condition is satisfied.

Supplementary notes
  • The event information received by an event job defined in a start condition can be passed to the succeeding unit. By setting a macro variable in an event job, you can pass the received information to all the jobs under the root jobnet governed by the start condition. For details about passing information from an event job, see 2.4.4(6) Passing information received by an event job in the JP1/Automatic Job Management System 3 System Design (Work Tasks) Guide.

  • When one of the event jobs defined for a start condition detects the same event in succession, the order in which those events are detected may differ from their actual order of occurrence, due to the communication status or other factors. There may be situations, however, when the order in which the start condition is satisfied by each event needs to match the order in which the events actually occurred, because the event information is to be passed to the succeeding job, for example. In such cases, use the event order option. However, when this option is used, the number of events that can be processed in a specific length of time is fewer than when this option is not used.

    For details on setting the event order option, see 6.3.2 Setting the event order option in the JP1/Automatic Job Management System 3 Configuration Guide for a Windows host, or 15.3.2 Setting the event order option in the JP1/Automatic Job Management System 3 Configuration Guide for a UNIX host. For details on estimating the number of events that can be processed with the event order option, see 3.1.5 Event monitoring performance in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.