Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!ames!ucbcad!ucbvax!CS.UCL.AC.UK!CHAA006%vaxb.rhbnc.ac.uk From: CHAA006%vaxb.rhbnc.ac.uk@CS.UCL.AC.UK Newsgroups: mod.computers.vax Subject: Removsl of ALLOCATE feature Message-ID: <8612112122.AA04899@ucbvax.Berkeley.EDU> Date: Thu, 11-Dec-86 16:22:38 EST Article-I.D.: ucbvax.8612112122.AA04899 Posted: Thu Dec 11 16:22:38 1986 Date-Received: Sat, 13-Dec-86 22:24:05 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 12 Approved: info-vax@sri-kl.arpa I would suggest pointing your users at an alternative set of DCLTABLES vias SYSUAF, and creating these from the normal DCLTABLES using the Command Definition Utility, while deleting the ALLOCATE command. Something like $ Set Command /Table=Sys$Library:Dcltables /Out=Sys$Local:Clitables - /Delete=Allocate Note that the output table name must be different from the input table name, even though it is in a separate directory, because it will subsequently need to be INSTALLed concurrently with the original, and VMS allows only one image of each name to be installed, regardless of directory. ** Phil.