jl%dac.triumf.cdn%ubc.CSNET@CSNET-RELAY.ARPA (John Lloyd) (02/07/86)
I'd like to add my vote to Roy Omond's problem (files developing "new
owners") where one or more files in a directory have their ownership
spontaneously changed. We've seen this about once, but have such little
(and old) evidence than an SPR seems almost embarrasing ("And how many
flashing lights did this UFO have? Three you say?")
Another XQP quirk that is kind of funny is the actual, not
architectural, limit on file versions. I accidentally let a batch job
continuously resubmit itself over a weekend on an 8600. 29,556 versions
later the job crapped out with "unsupported file structure level" -- a
very scary message as we'd seen the same thing in VMS 4.0 when it
scrambled a volume set that sort-of got full. In 4.2 it only gives the
message. One-and-a-half CPU hours later, 5 hours elapsed, all 29,556
versions of the files were deleted from the directory with a $ DELETE
X.LOG;* command. I am NOT going to SPR that one either! I have no use
for 29,555 redundant reminders of the existance of human fallibility.
Not to criticize the SPR system, but these are problems I know have been
encountered elsewhere, and another 2-line SPR is going to be more noise
than help for VMS developers/fixers. Or is it?