HP3000-L Archives

September 1999, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tom Hula <[log in to unmask]>
Reply To:
Date:
Wed, 1 Sep 1999 18:47:07 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
Bill Lancaster wrote:
>
> 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
>


Thank you for your answer.  I guess I was thinking about two different
problems at the same time, lowering the priority for the Speedware jobs,
but also insuring that both types of jobs ... ds and es ... can get in
and run at the same time.  Right now, I am running with just one job at
a time.  So, using one of the new process queues would work well ...
that is, if they are working and the bugs are out of them.  I am on 6.0
and haven't been anxious to try the the process queues after hearing
about problems people were having with them.
        Tom Hula
        Victor S. Barnes

ATOM RSS1 RSS2