HP3000-L Archives

November 1995, Week 4

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:
"R. Van Valkenburgh" <[log in to unmask]>
Reply To:
R. Van Valkenburgh
Date:
Fri, 24 Nov 1995 03:59:48 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (10 lines)
Another possible cause: very busy CPU.  The default case for sessions is
a higher priority than jobs.  Jobs with the *EXEC have finished the INIT
state and are just beginning the EXEC state --but really haven't done so.
 A job not being aborted after an ABORTJOB is another symptom of this
type of problem.  What happens is that all of the available CPU cycles
are being consumed by (higher priority) sessions with none left for
(lower priority jobs).  Remember a job needs CPU time to abort....
 
Regards,

ATOM RSS1 RSS2