From: MERC::"uunet!WKUVX1.BITNET!MacroMan" 29-MAR-1993 10:51:32.27 To: SYSMGR@IPG.PH.KCL.AC.UK CC: macro32 Subj: Re: SHOW$DEBUG >> Also, if you define the logical "SHOW$DEBUG" to be TRUE or 1 or, I >> believe, just about anything... A "SHOW DEVICE D" should give you a >> little more insight. > >Ace! Do you know of any other similar hooks -- if so I'm sure there's lots >of others who'd be interested. > > Yours, > Nigel Arnot > > NRA%ipg.ph.kcl.ac.uk@nsfnet-relay.ac.uk (internet) > NRA%uk.ac.kcl.ph.ipg@ukacrl.bitnet (bitnet) Yes! A few... First, let me explain how I found some of these. Since it could take a lifetime of Sunday's to peruse the source fiche for unique little hidden ditties..., I first dump the image of interest looking for ascii strings. If they don't look like command line arg't labels or other documented strings, they're candidates for source fiche perusal. (Unfortunately, my fiche is still fiche(film) -- no CD-ROM! I do have a friend that will look up things for me on his latest and greatest version CD :-) ) Now.. If you want to tie up your terninal for a while try this. DEFINE NML$LOG -1 and then go into NCP. This logical turns on various levels of debug reporting for the network management listener (ie. the NICE protocol) You can define this to other values to select NICE debug information of interest and filter out others. Each successive bit turns on more information. Try defining FAL$LOG too! I have mine defined to FF_FF in the login.com. Now, DECnet file accesses to your account from a remote node will leave a wealth of info in the NETSERVER.LOG file. The above were commented out in my login.com so they were easy to find. I'll look up some others later but I have to give Ehud a chance first... (after he finishes his bagel!) BJS- /Brian Schenkenberger/Schenkenberg@Eisner.DECUS.Org/Space for Rent/ /VMS Software Support/Vitronics, Inc./Eatontown, NJ/(908) 542-0600/ /Independent Consult./Tmesis Consulting/Jackson, NJ/(908) 363-7551/ /@Monmouth-ETDL1.Army.Mil/CIS: 70253,114/