"Newman, Kevin:" wrote:

> I tried nscontrol killsess=#s3560.  I tried it many times.  Still nothing.
>
> I tried abortjob #s3560, I tried abortio 37, I tried another suggestion
> I found in the archives.... and did a warn #s3560 LOGOFF NOW.
> Nothing seems to be helping.  I have five PINs associated with this hung
> session.  Is there a tool that will let me kill a PIN?  Any other
> suggestions, other than "Reboot the machine"?

(donning my sig sysman hat...)  gee, we 'sit' here day after day talking
about how reliable and wonderful our mpe systems are (and they are...)  but
how many times -- each week(?) -- do we hear this complaint from someone?
it's happened to all of us.  is this solvable?  can the engineers in
bangalore (or state-side...) invent some clever solution to keep us from
having to reboot for (imo) a ridiculous problem?  (/hat)          - d

--
Donna Garverick     Sr. System Programmer
925-210-6631        [log in to unmask]

>>>MY opinions, not Longs Drug Stores'<<<