I have a process that kicks off about 50 Kix32 processes via Run. Each process is passed an argument that it uses to create an INI file with it's status & results. (that arg becomes the INI file name.) The child processes create the INI file in the TEMP folder, updating it as they process their task. When the process is done, the last thing id does is to move the INI file to a folder where the parent process is watching for the files to appear. It reads the INI file, updates the common database, and then deletes the file. If there are more systems to process, it spawns off another child task.
I limit the number of child processes to 50, which (in my environment) ramps the CPU utilization to 100%. I process data collection from about 300 servers in about 15 minutes this way. There are a few older systems that take longer, but the bulk are completed quickly.
FWIW - my "parent" process is actually a kix script configured as a system service using SrvAny.
Glenn
_________________________
Actually I
am a Rocket Scientist!
