Howdy, Bout wore my snipper out on this one. But to be to the point: Through various versions/patches/expresses of the MPE/iX OS which they botched and my own occsional/rare/near-non-existant clumsiness, there have been times when I reached the "care" threshold. As in "If I kill this process I face dire consequences". The consequences although in detail cannot be known but the larger view of killing the process is I don't *CARE*. I want it dead.....now! We will worry about the body count later. It's my head on the block and if I wanna choppit well.... I've wished for years that HP had the HARIKARI command available. Jim - saw in the paper that the railroad misrouted our rain shipment to Ft. Worth. Bodes ill - Trudeau -----Original Message----- From: Thomas Madigan [SMTP:[log in to unmask]] Sent: Friday, March 12, 1999 11:52 PM To: [log in to unmask] Subject: Re: STUCK JOBS (somewhat longish) X-no-Archive:yes <snip> <cussing and fuming> "Reboot the system." Intentionally shut down a *production* system and interrupt the work of several hundred users to terminate ONE stuck process. <shout> TOTALLY UNACCEPTABLE!! </shout> <snip> The time has long passed where HP needs to balance the slight possibility of corrupting files against the reality of having to bring everyone's production work to a screeching halt to terminate one offender. Especially if MPE is truly meant to be a "high availability" operating system. IMHO, "rebooting the system" is a LAST RESORT measure. If I ever feel the need to practice "rebooting the system," I'll whip together a few NT boxes, throw on a couple of Micro$oft apps and wait for the damn thing to crash. I shouldn't have to wait long. See you on the other side, Ross. </cussing and fuming> <snip>