3.4.3 Valid range of a start condition

(1) Setting the valid range

How a valid range is set for a start condition depends on the method of jobnet execution registration.

Planned execution registration or fixed execution registration

Select whether to use a start condition when defining a schedule rule for a jobnet. If you use a start condition, also set a valid range. The settings take effect when you register the jobnet for planned or fixed execution.

Immediate execution registration

When you register the job for execution, select whether to use a start condition. If you use a start condition, also set a valid range.

For details about registering a jobnet for planned, fixed, or immediate execution, see 4. Executing an Application.

You can specify the valid range of a start condition by setting an execution count and/or by setting a period (in absolute time or relative time).

Number of executions

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

Monitoring of the start condition continues from the time set in the jobnet's schedule definition until the number of executions initiated by the start condition reaches this value.

Period

• Absolute time

  Specify in absolute time when to stop monitoring.

  Monitoring of the start condition continues until the specified absolute time arrives.

• Relative time

  Specify relative to the monitoring start time when to stop monitoring.

  Monitoring of the start condition continues for the specified period (in minutes) from the time that monitoring of the start condition begins.

If the event defined in a start condition occurs outside the valid range set for the jobnet, the start condition is not satisfied and the execution generation is not executed. However, for planned or fixed execution registration, even if start condition monitoring has terminated, the monitoring starts again within the valid range when the next execution time, determined based on the jobnet's schedule rule definition, is reached.

To Page Top

(2) Valid range specified in absolute time

When you specify a valid range in absolute time, events are monitored from the time that monitoring of the start condition begins until the specified absolute time. The execution generations are executed for the number of events that occur within this period.

The following figure shows an example of setting an absolute time.

Figure 3‒49: Example of setting the valid range of a start condition (absolute time)

To Page Top

(3) Valid range specified in absolute time and number of executions

When you specify both a period and an execution count as the valid range of a start condition, monitoring of the event ends when either the specified time arrives or the number of executions reaches the specified count.

The following figure shows an example of setting both an absolute time and number of executions.

Figure 3‒50: Example of setting the valid range of a start condition (number of executions and period)

In the above example, when the number of jobnet executions reaches the specified count (2 times), subsequent occurrences of the event are regarded as invalid even though the monitoring end time (12:00) specified in the valid range has not yet arrived.

Cautionary notes

• When a base time (other than 00:00) is set for an upper-level job group, be aware of how the absolute times used to specify the valid range are handled in JP1/AJS3.

  The following figure shows how times are handled when the valid range of the start condition is specified in absolute time for a jobnet with a set base time.

  Figure 3‒51: Handling of absolute time specified as the valid range of a jobnet with a set base time

  Dates are calculated from the set base time, but times are handled as shown in the figure. For example, suppose that a jobnet is scheduled for execution on 8/2 using a 48-hour time format, and the valid range is set to 26:00 in absolute time. The jobnet's valid range in calendar time will actually be 2:00 on 8/4.

  To avoid this problem, if you are running applications at or after 24:00, we recommend that you use a 48-hour schedule without setting a base time (i.e., base time is 0:00).

• For a jobnet with a start condition, the schedule options (schedule skip and multi-schedule) are disabled for monitoring generations and execution generations. To specify a processing cycle by using a jobnet schedule, you need to consider the concurrent execution of monitoring generations rather than schedule options. For details about the concurrent execution of monitoring generations, see 3.4.5 Concurrent execution of monitoring generations.

• A jobnet that has a start condition and a set processing cycle is scheduled accordingly when you register it for execution. However, if an unlimited number of executions and an unlimited period are set as the valid range of the start condition, two or more generations may be placed in Wait for start condition status. When the start condition is satisfied, all the waiting generations will be executed at the same time.

Supplementary note

If you specify the valid range in absolute time, make sure that the specified time is later than the execution start time of the jobnet. If you set an earlier time, the monitoring generation will be set to Monitor terminated status as soon as it starts execution.

To Page Top