• Subject: RE: A Job Queueing Problem
  • From: "Kahn, David" <KAHN@xxxxxxxxxxxxxxxxxx>
  • Date: Sat, 20 Sep 1997 15:57:00 +0600

Pete Hall (peteh@earth.inwave.com) wrote:

>From "Kahn, David"
><KAHN@tengizchevroil.com>, the following was written:
>> Re-read Rudolf's original requirement carefully then repost saying
>> exactly what settings of those parameters you would use to fulfill it.
>Sorry Dave, I don't have it. Why? What did I miss?

I'm not so sure now, Pete. I'm beginning to think it might be me who's
missing something. Looking at Rudi's original requirement I didn't think
it could be done without creating a new subsystem.

He wanted to be able to run 3 concurrent jobs in the susbsystem. He
wanted to have a maxact of 1 for Q1, 2 for Q2, and 3 for Q3, but not
have 3 simultaneously active from Q1 and Q2. In other words, if a job
was active from Q1 the maxact for Q2 would have to change dynamically to
1; and if 2 jobs were active from Q2 the maxact for Q1 would have to
change dynamically to 0.

Now some sleight of hand has been worked with job priorities that solves
the problem in some way I can't quite figure. I can see it might solve
the real operational problem, but I can't see how it does what Rudi
actually said he wanted to do. It looks to me as though Q1 has
disappeared from the picture altogether.

Puzzled,  :-(

Dave Kahn - TCO, Tengiz, Kazakstan

e-mail:  kahn@tengizchevroil.com    (until September 30th)
         dkahn@cix.compulink.co.uk  (from  October 1st)
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].