We just had an exciting experience... We had some apparently important
reports that ran on Thanksgiving and did not get printed. We only keep two
day's worth of spool files on the system. So, we were restoring our STD
file, and from that, all of our spool files from Friday. Then we began to
get reports of slow system response time, and our N class (MPE 7.0)
consistently has sub-second response time for the application. After
checking some of the more obvious possibilities, I called Beechglen. Jon
Backus and Doug Werth found that the spooler was consuming all available
CPU. Apparently, the spooler was having trouble both spooling to print, and
having restore write files to OUT.HPSPOOL. That sounds like a bug. So,
beware!

Now, among the many challenges we have with how we handle printing is how we
store and restore our spool files, such that getting back some of our spool
files means restoring all of them. There has to be a better way. Short of
buying a product, what are some better ways?

Greg Stigers

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *