RE: data queue's and locks

[Evan Harris <spanner@xxxxxxxxxx>]

Hi Rob

Whether this is an ugly technique or not is up to you but....

When your dataqueue server job starts it could write the job details 
to a user space (or a data area, but I prefer user spaces). Your 
shutdown job could then check whether the dataqueue server job is 
active by using the job details contained in the user space.

If the user space is not there - job has ended
If the job in the users space is not active - job has ended
Otherwise, send the shutdown entry

You could/should also add code checking for ending controlled, ending 
immediate type stuff

Regards
Evan Harris

At 03:22 a.m. 22/02/2007, you wrote:


> Depending on how many jobs are running and how long it takes to 
> retrieve the list of jobs you could still have a situation where the 
> job ends after you have made the API call and before you write the 
> shutdown entry.  The job would be in the returned list but not 
> actually active.  It would be rare but I have seen it happen with a 
> command I wrote to check for active jobs some years back.
>
> Rick