The following describes the job net statuses and provides examples of counting the message event occurrences.
When a job net only waiting for message events is paused
Even while the job net is in the paused status, message event occurrences are notified to the job net and counted for the number of occurrences. In the example below, msg1 and msg2 have occurred at the time of resuming, therefore, the job net will be started upon resuming. The message event occurrences will be cleared when the job net is started.
When a job net waiting for message events and startup time is paused
Here is an example in which the job net is started when both msg1 and msg2 have occurred and the startup time has come. Suppose the job net was in the waiting status before it was brought into the paused status.
The job net will remain in the paused status until it is resumed. If the execution conditions are satisfied when resumed, the job net will be started immediately and all the message event occurrences will be cleared.
In the example below, the job net has not been started as it is in the paused status, even though both msg1 and msg2 have been notified and the startup time has come. The job net will be started upon resuming and the message event occurrences will be cleared.
In the example below, the job net is in the waiting status as the startup time has not come yet at the time of resuming, even though both msg1 and msg2 have been notified while the job net is in the paused status. The job net will be started when the startup time comes.
When a job net only waiting for message events is disabled
The message event occurrences are not counted while the job net is in the disabled status. If the job net is disabled while msg1, which has occurred before the disable operation, is counted, the job will be started after the job net is enabled and msg2 is notified.
When a job net waiting for message events and startup time is disabled
Here is an example in which the job net is started when both msg1 and msg2 have occurred and the startup time has come. Suppose the job net was in the waiting status before it was brought into the disabled status.
The wait events which has occurred while the job net is in the disabled status will not be counted.
The disabled job net will be skipped at the startup time.
In the example below, the message event occurrence conditions will not be satisfied even when the startup time comes after the enable operation, because msg2 is not counted while the job net is in the disabled status even though msg1 is stored. The job net will be started and the message event count will be cleared when the message event occurrence conditions are satisfied.
When carried over of a job net waiting for message events and startup time is revoked
Here is an example in which the job net is started when both msg1 and msg2 have occurred and the startup time has come. It is supposed that the job net is in the carried over status before revoking the carried over.
The scheduled startup date and time will be re-scheduled to the next ones upon execution of the revoke operation and the job net will be in the waiting status. All the message event occurrences will be cleared when carried over is revoked. In the example below, msg1 is stored but the count for msg1 will be cleared when carried over is revoked. The job net brought into the waiting status by revoking carried over will be started when the next startup time comes and the message event conditions are satisfied. Then, the message event count will be cleared.
