Originally posted by: SystemAdmin

I asked another DSTX developer one time if the MAX CONCURRENT MAP INSTANCES = 0 settings on a system in the Integration Flow Designer meant that there was no limit on the number of concurrent maps. (In my experience, most of the DSTX settings use 0 to indicate no limit.)

His reply was "No, settings this to 0 means that no other maps can run concurrently." Is that correct? It doesn't seem so, as in another post, I saw where a developer changed this to 1 to get single threaded behavior.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

You are correct. 0 means no override limit on the number of concurrent threads for the map as specified in the Event Server.

b:3cdd5aa010Max Concurrent Map Instances[/b:3cdd5aa010]

The Max Concurrent Map Instances setting specifies the maximum number of concurrent mappings per watch.
This setting overrides the MaxThreads, WatchMaxThreads, and DisableMaxThreads Event Server settings.

b:3cdd5aa010MaxThreads[/b:3cdd5aa010]

The MaxThreads value is used to limit the number of map threads for all watches in an environment, provided that no other settings have conflicting values. If the following settings are not set to 0, then the MaxThreads value will be impacted:
♦ WatchMaxThreads
♦ DisableMaxThreads
♦ Max Concurrent Map Instances (a setting in the IFD).
MaxThreads=n
n - Specify the maximum number of maps (threads) that the Event
Server can execute concurrently. Range is 0 to 32,000. Default is 80.

b:3cdd5aa010WatchMaxThreads[/b:3cdd5aa010]

The WatchMaxThreads option is also known as Global Max Threads per Watch.
WatchMaxThreads=n

n - Global limit on the number of concurrent mappings per watch. This
number cannot exceed the MaxThreads value, which is the total
number of concurrent mappings overall. The range is 0 to 32,000.
The default setting is 0.
Note The Max Concurrent Map Instances setting in the IFD overrides the
MaxThreads, WatchMaxThreads, and DisableMaxThreads Event Server
settings.

b:3cdd5aa010DisableMaxThreads[/b:3cdd5aa010]

Use the DisableMaxThreads setting to disable the MaxThreads option.
DisableMaxThreads={0|1}

0 Setting is off (default).
1 Setting is on.

If set to 1, the MaxThreads value is disabled and the WatchMaxThreads value is used to place a global limit on the number of concurrent map executions per watch.
Note The Max Concurrent Map Instances setting in the IFD overrides the
MaxThreads, WatchMaxThreads, and DisableMaxThreads Event Server settings.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

MaxConcurrent Map instances does not over-ride any other settings. It is the maximum number of threads this map can use (as long as it is multi-threaded) even if watchmaxthreads and/or maxthreads is reached. Basically it is in addition to maxthreads. If maxthreads is 5 and maxconcurrent map instances on two maps is also 5, you can have 15 mapping threads running.

MaxConcurrent is useful if you have a map or maps that have to run, no matter how busy the Event Server gets. For instance, your error handling sub-system should have maxconcurrent set. If you have a heartbeat map used to determine system health, it should be set to 1.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

quote:558a409117MaxConcurrent Map instances does not over-ride any other settings.[/quote:558a409117]

According to the IFD documentation it does.

b:558a409117Max Concurrent Map Instances[/b:558a409117]

The Max Concurrent Map Instances setting specifies the maximum number of concurrent mappings per watch.
This setting overrides the MaxThreads, WatchMaxThreads, and
DisableMaxThreads Event Server settings.
However, my interpretation was the same as yours in that it applies to the map it is set on.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Based on what the person who wrote the code has told me, it works as I described. You can create a test case and see.

If you set maxthreads to 1, watchmaxthreads to 1, and have two multi-threaded maps, one with maxconcurrent set to 0 and the other set to 5, only the 5 setting map can run multi-threaded. The other map will only run in one thread. If you change maxthreads to 10, and leave watchmaxthreads at 1, the other map will still only run one thread.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Looks like the documentation needs updating.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

From the docs:
Max Concurrent Map Instances
The Max Concurrent Map Instances setting specifies the
maximum number of concurrent mappings per watch.
This setting overrides the MaxThreads, WatchMaxThreads, and
DisableMaxThreads Event Server settings.

What it should read:
Max Concurrent Map Instances
The Max Concurrent Map Instances setting specifies the
maximum number of concurrent mappings for the map where it is set.
This setting overrides the MaxThreads, WatchMaxThreads, and
DisableMaxThreads Event Server settings for the map where it is set.
This map can consume up to it's maximum setting, even if the MaxThreads value for all maps has been reached.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

Opened case against docs.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

I don't want to hijack the thread, but I have a related question. We have TX 7.5.1 on a SUN box with multiple processors. But our maps all run off one CPU. It's not a problem or a limitation as of yet because we aren't in production now and the load is low. But how would we get them to run on multiple CPUs?
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Should be new thread. :-) If the maps don't take 100% of the first CPU, they don't need any of the other CPUs. Normally Event Server will grab as much CPU and other resources as it needed. If you are using Command server, it is single threaded and can only run on 1 CPU.
It is also possible to limit the number of CPUs a process can use. If this has been set (in OS), there is not much the Event Server code can do.

You can run UI script and check "top" in the launcher.log file or run top yourself to see how much you are using.
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender