Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU Path: utzoo!decvax!decwrl!ucbvax!bbn-spca.arpa!grubin From: grubin@BBN-SPCA.ARPA (Gail Rubin) Newsgroups: mod.computers.vax Subject: Re: Set Protection=W:RWED/NAME_TABLE=LNM$JOB Message-ID: <8510222310.AA12194@UCB-VAX> Date: Tue, 22-Oct-85 13:25:18 EDT Article-I.D.: UCB-VAX.8510222310.AA12194 Posted: Tue Oct 22 13:25:18 1985 Date-Received: Wed, 23-Oct-85 13:26:20 EDT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 13 Approved: info-vax@ucb-vax.arpa We ran into this as soon as we brought up 4.0. But only for our system users who typically changed uic and default dir when helping someone else out. We called Colorado and they looked into it; they said there is NO WAY AT ALL to specify the protection on the job name tables at this time. No sysgen parameter or anything. Our workaround here is for those of us who are system types to just turn on sysprv and set default since in vms 4 if you create files in some dir owned by another uic, the files get the directory's uic, not yours if you have sysprv on. This doesn't apply to normal users. Sorry I can't be more encouraging. -- Gail Rubin