Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!mcnc!ecsvax!dfile From: dfile@ecsvax.UUCP (Dean File) Newsgroups: comp.os.vms Subject: Re: CLEAN IT UP FOLKS Message-ID: <3591@ecsvax.UUCP> Date: Fri, 24-Jul-87 14:47:49 EDT Article-I.D.: ecsvax.3591 Posted: Fri Jul 24 14:47:49 1987 Date-Received: Sat, 25-Jul-87 15:13:14 EDT References: <8707241511.AA19765@ucbvax.Berkeley.EDU> Organization: UNC Educational Computing Service Lines: 28 Summary: MicroVAX documentation In article <8707241511.AA19765@ucbvax.Berkeley.EDU>, graham@DRCVAX.ARPA writes: > > "...Those of us who have been running VMS systems for a while > > usually try to consult the documentation before yelling > > "SYS$ANNOUNCE logical name bug" or running to the net showing our > > stupidity. Then when we do find a legitimate problem unless it > > has a great impact on other systems we simply and quietly fill out > > an SPR instead of trying to show everyone how cute and clever we > > are." > > Excuse me, but it is not stupid to ask a simple question. VMS is a large > anf complex product. It has a *LARGE* documentation set. There is no such > thing as a stupid VAX question. The other side of this is that the MicroVMS documentation set is too small, the standard set that is. Perhaps there should be a comp.os.uvms group. Still, I agree with graham. Sometimes the solution is in the doc set, but is apparent only if you've been a DEC guru for ten years. It's very nice to have recourse to a group of DEC gurus who aren't going to flame you for not being one. > Whew! I feel better now. Whew! So do I. (The above opinions are personal and do not reflect the position of my employer.) Dean File