You may want to execute the same job net concurrently, such as for running aggregation processing for individual stores in parallel, as shown in the example below. In this case, consider concurrent execution using copy and startup.
You can execute multiple instances of the same job net at one time without increasing the number of job net definitions in the system as a whole.
Before starting concurrent execution using copy and startup, you must specify copy and startup in the property information of the copy source job net. Job nets for which you specify copy and startup are always copied and started.
The execution result for each job net that was copied and started is preserved; it is not overwritten. If the number of saved execution results becomes too high, performance may deteriorate. Therefore, if running concurrent execution that uses copy and startup, consider the following when configuring the number of job nets to save so that it is limited to the requisite minimum.
Number required for job net monitoring
It should not affect the job net execution performance
Refer to "Notes When Registering a Large Number of Jobs" in the Systemwalker Operation Manager User's Guide when determining the number of job nets and carefully verify operations when designing them.
