Walter asks:

"What might cause an MPE/iX 7.5 system to get into a loop constantly writing
the message "FWRITE TO TERMINAL FAILED" to the console and filling up the
log files?"

Bad programming. Seriously,... bad programming. Whatever program or section
it was that was sending the error should've aborted or aborted after a
certain number of loops.

What kind of program was running? Was it using View, V-plus, etc.
intrinsics? This doesn't sound like any error I've ever seen come from that
subsystem. If it was from a user logged on through telnet, and thus jinetd,
it's possible the error message tracked back through that mechanism to the
console.

Possibly the program is set to do an FWRITE, checks for an error, reports it
to the console, then tries again, and again, and again, to infinity. That's
where the bad programming takes effect.

Hopefully you can find out what program a job or user was running, and that
you have the source - or your application vendor does.

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