This is the second time in a week I've had to reboot our 3000 to get rid of a
job which wouldn't abort.  We're running RoadRunner (which hasn't generally
been a problem).  Backup goes fine and then a second job logs on to do a verify
using autoload and autoreply.

Last week, due to backup starting late and a heavily loaded system, our
operator thought that the verify was done and popped the tape out.  Result,
hung process.  No luck on ABORTJOB, ABORTIO or anything.  Shutdown to solve.

This week, for other reasons, backup took longer than it ought and I needed to
not run the verify job.  I was minutes too late in stopping it and it got
logged on.  I did a BREAKJOB just as it was starting to read the directory off
the tape.  A few moments later, after having solved the current emergency, I
did an ABORTJOB.  At that point, the main job process went away, but two
RoadRunner processes stayed around.  They were live processes (using CPU),
one on Break Wait, the other on Timer Wait (waiting on the one on Break).
Tried a bunch of things, called HPRC--that call is still going.  Eventually I
was left with rebooting.

In both cases, a

=shutdown

didn't even get to shut 1.  I waited until I was convinced it wasn't going to
go down and then did a ^B RS.

Anywho, this message is mostly a heads-up.  Hope y'all don't face the same
thing.

Ted
--
Ted Ashton ([log in to unmask]), Info Serv, Southern Adventist University
          ==========================================================
At the age of eleven, I began Euclid, with my brother as my tutor. This was one
of the great events of my life, as dazzling as first love.  I had not imagined
there was anything so delicious in the world. From that moment until I was
thirty-eight, mathematics was my chief interest and my chief source of
happiness.
                        -- Russell, Bertrand (1872-1970)