Increasing the number of concurrent copies that a NSM can handle
Last Modified: 2009-Jan-24
Q:How can the number of concurrent copies that a NSM v2.0 Sentinel,or an NSM v2.5 Agent be increased?
A:There are actually two answers to the question. One is at load time, and the other is used re-entrantly so that the parameter can be changed on the fly.
Applies to: 
eDirectory platform / NSM v2.x
Note: The Event NLM in NSM 2.5 has been renamed to NSMEVENT.NLM from the v2.0 FSFEVENT.NLM.
- If the Sentinel/Agent NLM is already running the maximum number can be changed by typing the following at the system console:
Where the xx is a number between 1 - 99. The default is 3.
v2.0 - fsfevent maxcopydir=xx
v2.5 - nsmagent maxcopydir=xx - If Event NLM is not running it can be loaded with the maxcopydir switch by typing at the system console:
v2.0 - SYS:/FACTORY/FSFEVENT -S EngServ -maxcopydir xx
v2.5 - SYS:/FACTORY/NSMAGENT -maxcopydir xx
In NSM v2.0, the maxcopydir switch can be added to the FSFEVENT load line in the AUTOEXEC.NCF so that the FSFEVENT.NLM gets loaded each time with the maxcopydir option.
In NSM v2.5, the maxcopdir setting is persistent across restarts with out adding the switch to the AUTOEXEC.NCF.
