I saw a similar problem on a 969-020 several years ago. It seemed like
problem was always on one frequently modified dataset.  I was convinced we
had an Image or database tool problem.   It turned out to be a SCSI card
that was bad.  The problem had been ongoing for almost five weeks.  We
finally found it when the system eventually aborted... because the extent
map for a file had been mangled...by the interface on the way into memory.
(extent map was pointing to a drive that did not exist).

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