I vote a strong *yes* to CI enhancements to show why the process is hung.
        Don Inghram, Systems Mgr.
        The Christian & Missionary Alliance
        Colorado Springs, CO  (719) 265-2154
        [log in to unmask]


> -----Original Message-----
> From: Scott McClellan [SMTP:[log in to unmask]]
> Sent: Thursday, April 29, 1999 8:23 AM
> To:   [log in to unmask]
> Subject:      Re: How do I kill a hung session ?
>
> > -----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?