RE: Multiple Jobs reading from same data queue-who's turn is it?

There can be more than one JOBQ, and a JOBQ can be set to process more than
one job at a time. Let's assume you have only one JOBQ and it is
multi-threaded.

When interactive job sends job to JOBQ, the CL assigns a priority.
All low priority jobs are to be completed before a higher number job is
done, but only after the current running job is completed.

When the job arrives in JOBQ, it gets a number which is based on time stamp
of arrival. Jobs with same priority will get started in that arrival
sequence.

-
Al Mac
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Murvin
Sent: Thursday, March 12, 2009 10:53 AM
To: Midrange Systems Technical Discussion
Subject: Multiple Jobs reading from same data queue-who's turn is it?

Hello,

We have three server jobs, running at interactive priority, that all
read from the same data queue to do a specific task. What I do not know
is how the system decides who gets to read the next data queue entry.
Does is just go in sequence (job 1, then job2, job 3, then back to job
1) or is it some kind of first come first served process? If job 2 is
currently processing a request and it is normally job 2s "turn" when
another request arrives at the data queue, does the request wait for job
2 or does it go to the first job that is ready to receive the request?

I am concerned that since these jobs are part of an interactive process,
that we might get hung up waiting for one of the server jobs to finish
when there are other server jobs available to process the request.
Previously, each job called the server process directly, so each
interactive job had their own copy of the processing programs.

Thanks

Dave