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!watmath!clyde!burl!ulysses!ucbvax!info-vax From: Tli@USC-ECLB.ARPA (Tony Li) Newsgroups: mod.computers.vax Subject: VMS conventions Message-ID: Date: Sun, 2-Mar-86 02:18:00 EST Article-I.D.: ECLB.TLI.12187416490.BABYL Posted: Sun Mar 2 02:18:00 1986 Date-Received: Sun, 2-Mar-86 19:24:00 EST References: Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Tli@Usc-Eclb Organization: The ARPA Internet Lines: 26 Approved: info-vax@sri-kl.arpa From: Brent Sterner What do most of you call your generic utility area? Gee, we call ours SYS$SYSTEM! No foolin! We created a directory structure [USCCOMMON.] and then did $ define SYS$SYSROOT sys$sysdevice:[sysn.],sys$sysdevice:[usccommon.],- sys$sysdevice:[v4common.] !Modulo switches and other stuff. Works like a CHAMP! All of your utilities look like they really are in SYS$SYSTEM. Dec stuff doesn't mingle with yours! 2nd; is there a *good* technique for adding help files for such items as non-command thingies (for example *help terminals* for a list of local terminal types. I note (I think) that DEC does not help in this matter; I would kile NOT to edit DEC help files due to future upgrades. Make a help library (FOO.HLB) and do $ define/system HLP$LIBRARY FOO.HLB Then, $ HELP terminals does exactly the right thing... ;-)