Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!ULKYVX.BITNET!SYSMSH
From: SYSMSH@ULKYVX.BITNET.UUCP
Newsgroups: mod.computers.vax
Subject: re: sys$specific DCLTABLES
Message-ID: <8701131526.AA07126@ucbvax.Berkeley.EDU>
Date: Sun, 11-Jan-87 11:49:00 EST
Article-I.D.: ucbvax.8701131526.AA07126
Posted: Sun Jan 11 11:49:00 1987
Date-Received: Tue, 13-Jan-87 19:25:44 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of Louisville
Lines: 15
Approved: info-vax@sri-kl.arpa


Hey I bet it was TDMS that did it to you, those other packages do the right
thing.  It may have looked at the VAXCLUSTER sysgen parameter...since you
only have one 8650 you may have that set to 0.  If 0 it may decide that
you don't have a common system disk.

I had a similar experience on my cluster.  I installed a recent upgrade of
the MINITAB statistical package and it created a sys$specific DCLTABLES,
protected it (o:rwe,s:rwed,g,w) and replaced the installed image.  Unprivileged
users would log on and get booted out with a protection failure on the
command tables!!   groan!!

Mark Hittinger/systems programmer iv/ocis south center
University of Louisville/louisville, ky 40292
sysmsh%ulkyvx.bitnet@wiscvm.wisc.edu