RE: Detemine job completion status

My apologies, Scott.  I misunderstood your question and the nature of
Spawn().  My invalid assumption was that WaitPID() would have to be executed
after each Spawn(). 

Combing the job log might make sense if the process is itself a submitted
job.  The assumption could then be made that anything submitted by the job
needs to be completed before the next step.  That would, of course, only
work once per job.  My transmission and retrieval process could work this
way. 

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx

<clip>
My suggestion was to use spawn() to submit jobs. You can use it to submit as
many copies as you need.  Each time you call it, it returns an integer 
called a "pid" (short for "process id").  You can then use various APIs to
wait for that pid to complete.
<clip>
why would you ever want to monitor all jobs, even those that have nothing to
do with your current process?
<clip>