A105@UWOCC1.BITNET (Brent Sterner) (03/13/86)
TSC called me yesterday with the following information about UIC
corruption. Apparently it requires volume sets and a privileged user
running. (Sorry I have no more information about what exactly "running"
means in this context.)
The official reply is "fixed in a future release". Apparently this
one is a design flaw, so it won't get fixed with a simple patch. TSC
is running a field test of VMS 4.4, and it isn't fixed there, although
it is I guess possible that it might get fixed before 4.4 hits the
streets. TSC OKed my notifying the net about this status. (Thankyou.)
My opinion is that this sort of bug ought to be given VERY HIGH
PRIORITY. (I don't know the priority assigned by Digital; it may in
fact be VERY HIGH.) Data corruption simply cannot be tolerated,
especially on mainframe machines. I intend to ask at DECUS about
progress on this one. Apparently there were a LOT of SPRs about it.
Perhaps lots of us asking about it at DECUS might expidite matters.
If Digital is listening, thankyou if you're pressing this one.
Brent Sterner
Computing & Communications Services
Natural Sciences Building
The University of Western Ontario
London, Ontario, Canada
N6A 5B7
Telephone (519)679-2151 (secretary)
2167 (direct)