Tom,

Putting the Speedware jobs in the E queue makes sense.  In this case, you
may want to be sure to have the E queue overlap the D queue, not the C
queue.  If you do overlap the E and D queues, you should give some thought
on where in the D queue you want the E queue to be.  Consider something
like 234,236.

The new queues you mention that had problems are the process queues.  They
were the new multiple job queues, two completely different animals.

Bill

At 05:30 PM 9/1/99 -0400, Tom Hula wrote:
>This question if for Bill:
>
>I have an environment that is mostly Cobol and Protos (didn't I say
>Cobol already?).  However, I have one third party application that is
>written in Speedware and uses Allbase.  All of the other applications
>are very efficient ... interactive or job ... but the Speedware jobs are
>definite hogs.  I would like to put them somewhere where they don't
>affect the rest of us, like preferably on another computer.  But since
>that isn't possible, would it make sense to run all the Speedware jobs
>at priority ES or run in one of those new user defined queues at
>affective ES priority (Are the new queues still having problems?) so
>that I could always automatically have all the regular jobs pop in and
>run?
>        Tom Hula
>        Victor S. Barnes
>
>