Case 1: Different map instances run at the same time, if all sources and targets are different.

How run options are selected might affect the length of time a map instance is in process. Assume run options are set as one of the following combinations:

Select unique work file names or work area in memory and select no log file.
Select unique work file names or work area in memory and select unique log file names.

In this case, each map instance is independent and the length of time each map instance runs depends only on the amount of processing time associated with the size of the data and the mapping rules used.

If sources and targets are independent, and unique work files are used, but map instances share log files or other map system resources, you might see map instances in process run longer than expected. This occurs because the Launcher will initiate an instance based on available event triggers and then waits for map system resources to become available.

Note: Sources can be the same if they do not have the potential of a map writing data to it. See Different Maps That Use the Same Source.

Note: If you use work files with the WorkFilePrefix setting of MapName (available under the Workspace setting; see MapSettings > WorkSpace), be sure to use the retry option if multiple map instances can run at the same time. If a retry is not set, the map will fail to run if these resources are in use.

You might also see this same effect if a source or target resource is required, it cannot be shared, and it is in use by an application unknown to the Launcher. In this case, be sure to use the source or target retry option, or the map instance will fail to run.