Are you having response time problems. With the current settings the EQ
can only get CPU if the CQ and DQ are not using all the CPU. The catch
might be that the EQ jobs have the same databases open as the CQ jobs
and they get their priority boosted when a CQ or DQ job locks
(put/delete semaphore  most likely). Otherwise you have the correct
settings for favoring the CQ and DQ. For good response time its normally
best to have shorter time slices for all of the queues.

Why do you want to slow down the E queue, the system was designed to
favor the the highest priority processes(CQ with your settings) and then
  give everything else to the lower priority processes(DQ then EQ) with
your settings...If you really want to slow down the EQ processes write a
program that does a loop and pauses occasionally (experiment with best
value) and then put it in the DQ (if that's higher priority then EQ).

Most recommendations about queue settings are really trying to keep DQ
and EQ starvation from happening and with your settings if the EQ is
running then starvation is not occurring...




KENT WALLACE wrote:
> I would like to slow jobs down in the "E" queue.  How should I change the "E" queue.
>
> The current settings are:
>
>
>                     ------QUANTUM-------
> QUEUE  BASE  LIMIT  MIN    MAX    ACTUAL  BOOST  TIMESLICE
> -----  ----  -----  ---    ---    ------  -----  ---------
>  CQ    152    200   1      2000   1       DECAY    200
>  DQ    202    238   2000   2000   2000    DECAY    200
>  EQ    240    253   2000   2000   2000    DECAY    200
>
> Thanks
> Kent Wallace
> Boise Id
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *