3.4.1 Detailed considerations

(1) Valid range of start conditions

Consider the range in which the occurrence of an event defined as a start condition is to be monitored. You can specify the valid range as a number of executions or a specific time. Set the valid range of a start condition when defining the schedule rules for a jobnet.

Number of executions

Specify the number of times that the jobnet can be executed from the time that monitoring for the start condition begins.

Period

Monitoring of the start condition continues until the specified time arrives. You can specify the time as an absolute or relative time.

To Page Top

(2) Operation when multiple event jobs and custom event jobs are used in a start condition

When multiple event jobs and custom event jobs are defined, consider whether you want the start condition to be satisfied when all the events occur (an AND condition), or when any one of the defined events occurs (an OR condition).

To Page Top

(3) Concurrent execution of monitoring and execution generations

When you execute a jobnet with a start condition, generations which monitor for the occurrence of the events defined in the start condition (monitoring generations), and generations which are executed when the start condition is satisfied (execution generations), are both generated. For jobnets with start conditions, consider whether to allow concurrent execution for monitoring generations, and for execution generations.

Concurrent execution of execution generations

In situations where the start condition is satisfied multiple times, consider whether you want a new generation of the jobnet to run concurrently with the previous generation or to wait until the previous generation has ended. This behavior is determined by the concurrent execution setting in the jobnet definition.

If you disable concurrent execution, consider whether to hold execution generations as described in (4) Holding execution generations.

Concurrent execution of monitoring generations

For jobnets with a start condition and a processing cycle, consider how you want a new monitoring generation to be executed if the previous monitoring generation is still running when its start time is reached. You can have the new monitoring generation execute concurrently, wait until the previous monitoring generation has completed, or skip execution altogether.

To Page Top

(4) Holding execution generations

If you disable concurrent execution, you can choose whether to hold execution generations that satisfy the start condition. You can select from the following behavior:

• Does not stay with skip

  Execution generations in Wait for start cond. status are not held, and transition to Skipped so not exe. status.

• Stay without skip

  Execution generations in Wait for start cond. status are held.

To Page Top

(5) When a jobnet with a start condition ends abnormally

Consider the behavior of the system after a jobnet with a start condition ends abnormally. You can select from the following behavior:

• Start execution of jobnet

  After ending abnormally, the jobnet starts at every subsequent occurrence of the event being monitored by the start condition.

• Hold start of jobnet

  After ending abnormally, the jobnet is placed in Held status, or remains in Wait for start cond. status with future execution suspended.

• Stop monitoring of start conditions

  After the jobnet ends abnormally, the system stops monitoring for the start condition.

To Page Top

(6) Other considerations

Also consider the following:

• How often a condition will be satisfied within a given time frame^# (how many event jobs and custom event jobs are likely to be executed).

  #: You can use this information when you estimate event job and custom event job performance.

To Page Top