HP3000-L Archives

January 1996, Week 2

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:
Reply To:
Date:
Fri, 12 Jan 1996 16:01:42 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines)
Jeff wrote:
> >:ALTJOB on an EXECuting job only requires evaluating whether a different job
> >can now launch because we just freed up a slot in the queue we were in.
>
> Yuck... I see no need to alter the queue after the job reaches INTRO/EXEC.
> No, no, no; overly complicating things.
 
Hmmm. Ok, maybe.  The desire to move a job from the SHORT queue to the LONG
queue once it is determined that it's really going to take three hours
instead of three minutes seems pretty basic though. The alternative is to
increase the LIMIT on the SHORT queue by one, but then you have the problem
that when the job finishes, the limit on SHORT is one too high.  This is
exactly the kind of problem this enhancement is trying to address.  I think
at least as many changes will be made with :ALTJOB to running jobs as to
waiting jobs.
 
G.

ATOM RSS1 RSS2