A105@UWOCC1.BITNET (Brent Sterner) (02/27/86)
Sorry to bother with such a trivial query; it comes from above.
We have a utility area called sys$utility, whit very little there
except directory files to various utilities, and a generic *utility.com*
file. I've been asked why it wasn't called PUB: like our DECsystem-10
(and copied by our CYBERS running NOS; they use /UN=PUB). What do most
of you call your generic utility area?
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.
Thanks for the assistance.
Brent Sterner
Computing & Communications Services
Natural Sciences Building
The University of Western Ontario
London, Ontario, Canada
N6A 5B7
Telephone (519)679-2151 (secretary)
2167 (direct)Tli@USC-ECLB.ARPA (Tony Li) (03/02/86)
From: Brent Sterner <A105%UWOCC1.BITNET at WISCVM.WISC.EDU>
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...
;-)