My understanding is it is first come first served.
As for waiting for "Job 2", I think you are misunderstanding the process.
When your server program receives the dataq entry, it is done with the
dataq. It does not hold it while it processes. So if your dataq has
entries in it, no server job will need to wait for an entry to process. It
will just grab the next available entry.
All 3 jobs should be processing different requests simultaneously unless
there are no more entries to process. In which case the server job will
wait the amount of time specified on your call to QRCVDTAQ.
HTH,
Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi
Young i Professionals
http://www.youngiprofessionals.com
Dave Murvin <davem@xxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/12/2009 10:57 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc
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
midrange.com
