RE: Detemine job completion status

Let's say, for example, that one has an application that sends and receives
data from other entities and let's also say there are two or more of these
entities.

This application submits jobs that perform the transmission and retrieval of
data, which update files used later in the application for reports.  The
transmission and retrieval of data needs to happen before the reports can be
printed.

Now the application could submit the jobs in series as you suggest, but that
would probably be an inefficient use of resources.  Submitting the jobs in
parallel and waiting for the jobs to be completed makes more sense to me,
but that's just my opinion.

In the case above, I just built a work file that's updated with the name of
each submitted job and then used the TAATool command for job status to
determine if the jobs were complete.

If the record for the job was still in the work file and the job was not
active or on the job queue, I assume the job ended abnormally.

Perhaps something similar would work in this case? 

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


<clip>
Why on earth would you want to do that?!

If you want to submit a job and wait for it to complete -- that makes sense
-- just use spawn() and waitpid().  But why would you want to wait for any
job that's ever been submitted from the current one?
<clip>