HP3000-L Archives

April 1999, Week 5

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:
Scott McClellan <[log in to unmask]>
Reply To:
Scott McClellan <[log in to unmask]>
Date:
Thu, 29 Apr 1999 10:22:50 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of Simonsen, Larry

> one of the questions which I need to know is why is a process hung.  what
> resource is it waiting on that it does not respond to the abort job.  if I
> knew why then there could be better resolution as to the cause and
> correction for future events.
>
> is there a way of showing for a particular job/pin the current state of
> critical/non-critical and some resource waiting for?
This is (IMO) a very reasonable request. There are some enhancments in
this area "being considered". There is no official commitment at this time
to do this, but it is a possibility.

The exact questions "why is a process hung" is very difficult to answer
currently. A derrivative of that question "what is process (n) doing? what
state is it in? is it critical? etc" is more doable.

Leading question: would there be a lot of support for some new CI funcitons
(eg: pinfo, etc) and enhancments to the :SHOWPROC command to show the
required information?

ATOM RSS1 RSS2