Job nets are started individually based on their execution conditions and startup days, but it is also possible to execute job nets in a fixed order, as is the case with jobs.
However, if you simply set staggered execution times for two job nets so that the second one can carry on after the processing for the first one has finished, there is a chance that the second job net will start before the first job net has finished.
To ensure that the second job net waits for the first job net to finish processing before it starts, use either of the following methods to specify the job net execution order:
Job net layering
A job net can be registered as a job within another job net. (This is called "job net layering.") By using job net layering, job nets can be scheduled by connecting job net icons on the screen to create a flow diagram.
Linking with message events
This method involves scheduling the job nets so that the second job net is triggered to start when it receives a message from the final job in the first job net.
To generate a message event, register the jobschmsgevent command in the final job of the first job net. For the job net that is triggered to start by receiving the message, specify the settings in the Standard information and Message tabs of the Job Net Properties window.
Grouping
Grouping multiple job nets enables you to execute the job nets in order. You can schedule the job nets by connecting them using the flow for creating a group and then visually creating a flow diagram.
These methods have their advantages and disadvantages, so determine which method to use according to the actual operation.
Scheduling method | Advantage | Disadvantage |
|---|---|---|
Job net layering | The relationship between the first (preceding) and second (succeeding) job nets can be edited and checked visually using a flow diagram. Job nets are executed as specified by the flow, making it easy to keep track of the operational status. | Only job nets within the same project can be linked. |
Linking with message events | Job nets can be linked to job nets in other projects or on other systems. | It is difficult to check the operational status of job nets, and the operation can easily become complicated as a result of message events being cleared. |
Grouping | The sequential relationship can be visually edited and confirmed using the flow. A message or time can be set for starting job nets in a group. | This function groups job nets to be started at a certain time once a day, and was designed for changing the configuration of job nets executed on certain days, so numerous restrictions apply. |
If you are not certain which method to use, it is recommended to use job net layering, which is easy to understand, has fewer restrictions, and where the relationship between the first and second job nets can be edited and checked visually using a flow diagram.
