A From:	SMTP%"RELAY-INFO-VAX@CRVAX.SRI.COM"  2-JUL-1993 17:10:34.15  To:	EVERHART CC:	+ Subj:	Info-VAX: "Advanced" Common Questions   ? X-Newsgroups: vmsnet.misc,comp.os.vms,news.answers,comp.answers . Subject: Info-VAX: "Advanced" Common Questions0 Message-ID: <info-vax-3.19930702.135331@dmc.com> From: munroe@dmc.com Date: 2 Jul 93 13:56:01 EDT  Followup-To: vmsnet.misc Expires: 13 Aug 93 00:00:00 GMT E Organization: Doyle, Munroe Consultants, Inc., Hudson, Ma. 01749, USA  Approved: munroe@dmc.com
 Lines: 476 To: Info-VAX@KL.SRI.COM  X-Gateway-Source-Info: USENET    Archive-name:   info-vax/part03  Last-modified:  1992/09/05  I [Changes since last posting: Added a description of how to usefully debug  with ANALYZE/PROCESS/IMAGE.]  '            The Info-VAX Monthly Posting '            ---------------------------- 1            PART 3 -- Advanced "Common Questions". ?            (Coordinated by Dick Munroe, written by many others)   M (Part 1 is an introduction to Info-VAX.  Part 2 is Beginner Common Questions. & Part 4 is about how to find software.)  ' Save this message for future reference!    Table of Contents:  L ,BAC   -- Advice on how NOT to backup your VAX            updated 1989-08-036           LEICHTER@VENUS.YCC.YALE.EDU (Jerry Leichter)D ,BOOT  -- Booting a system whose disk is full.		          1992-08-12& 	  rankin@eql.caltech.edu (Pat Rankin)5 ,DIR   -- Why is my directory so slow				  1992-08-09 ' 	  Various people from vmsnet.internals L ,SIG   -- How to set up automatic signatures, etc.          added 1989-09-29.           CADS_COLE@GALLUA.BITNET (Kevin Cole)L ,FLA   -- No question is stupid...                          added 1989-10-02)           [A reminder to "us gurus" -TAL] 6           FASTEDDY@DFTNIC.GSFC.NASA.GOV (John McMahon) ,IMAGE-DUMP-ANALYSISE        -- Debugging using ANALYZE/PROCESS/IMAGE.	    added 1992-09-05 " 	  Martin Jensen <mjensen@BBN.COM># 	  George Carrette <gjc@mitech.com> L ,MCR   -- About MCR (Bruce Wright)                          added 1989-10-02           rti!bcw@MCNC.ORG  C (the ",BAC", ",SIG", etc are keywords.  If you search for that text J (including the ",") you will be brought to the beginning of that article.)  E ---------------------------------------------------------------------  ,BAC Subject: VMS Backup tipsM >From LEICHTER@VENUS.YCC.YALE.EDU ("Jerry Leichter") Tue Aug  1 10:01:00 1989 	 Lines: 74   N >[Various messages concerning long BACKUP times on a MicroVAX II, along with a$ >recommendation of the command line:H >   $ back/log/ver *.*/ignore=inter mua0:backup.bck/sav/buf=5/blo=17408- >        /nocrc/group=0  >] > F > I think that Bob's response addresses part of the major problem withI > BACKUPs on uVAX-IIs:  that of CRC.  On uVAX-IIs, the CRC instruction is F > emulated in software as opposed to being in hardware as it is in itsK > bigger brothers.  As you might imagine, doing CRCs takes forever on a II. / > /NOCRC is a MUST in your BACKUP command line.   I In general, both of these pieces of advice - ESPECIALLY the first one!  - L are EXTREMELY BAD.  They are the equivalent of "Locksmiths are SO expensive,J I won't bother to install locks on my front door".  Such advice might makeC sense in some parts of the country, but try it in New York City....   J Before considering this advice, decide for yourself just WHY you are doingI backups.  Is it because you've heard that it's a good idea, or because it L appears on your job description, but you don't REALLY expect ever to USE allK those tapes you are writing?  Or is it because you want a safe copy of your E data in case something goes wrong with your disk, or in case you just * acciden- tally delete something important?  K If it's the former, I'll suggest that you can actually make BACKUP run even J faster; just add /CREATED/SINCE:TOMORROW.  Try it - you should see amazingI results.  In fact, the results will be so good that you should be able to 5 save all the typing for those other tacky qualifiers.   9 It it's the latter, consider what chances you are taking:   J  - If you use /NOCRC, you are relying on the error detection capabilititesK of the tape hardware.  This varies in ability to detect problems, depending F on the kind of tape and the density.  Even at its best, it provides noG protection against problems with the tape interface, with the bus, with D memory, and so on.  ALL of these are known potential failure points.  I - If you add /GROUP=0, you are disabling BACKUP's ability to recover from K errors that develop on the tape while it is in storage, among other things. J What you are getting in return is about 10% more data on the tape.  Sounds  like a very poor tradeoff to me.  L  - I don't know how the block size of 17408 was selected.  The default valueI (2048) was chosen by people with some data about tape failure statistics. I It's a tradeoff:  The larger the block size, the more data you can fit on G the tape - but the larger the probability of two blocks in a redundancy L group suffering simultaneous errors, so that the data is irretrievably lost.  H Of course, since redundancy groups have been disabled (by /GROUP=0) this makes little difference anyway.   H  - Also about /BLOCK:  The combination of a large blocksize with a largeJ buffer count can cause a reel-to-reel tape to run off the end of the reel.H (Tapes have reflective "end of tape" markers well in from the end of theI tape, but if enough data is already "in the pipe" it can be impossible to > stop the drive in time.  Ever try threading a tape backwards?)  G I can think of almost no reason to play with the redundancy group size, F except for things like BACKUP savesets used to transfer stuff across aE network where errors are unlikely and you can get another copy of the  damaged stuff if you need it.   > I can think of few reasons to play around with the block size.  J I personally can't imagine a serious backup policy based on use of /NOCRC,G at least as a universal policy.  (I suppose you MIGHT do weekly backups J /CRC, and nightly incrementals /NOCRC, figuring that the cost of having toK go back, at the very worst, to the weekly backup is small enough to justify  the additional risk.)   K There are significant tradeoffs to be made here.  "Speed of backup" is only L one factor.  You have to decide for your own site how to balance this factorE against the others.  But do it in an informed way!  Also, be ready to J re-examine your conclusions as the data change:  BACKUP in VMS V5.2 shouldJ be much faster.  In particular, the CRC algorithms have been SIGNIFICANTLY sped up.          -- Jerry   E ---------------------------------------------------------------------  ,BOOT   9 >Subject: Re: How to boot VMS from a failed AUDIT writing * >From: rankin@eql.caltech.edu (Pat Rankin) > I >In newsgroup vmsnet.misc, article <1992Aug10.142728.4397@mic.ucla.edu>,\ 0 > shinn@agsm.ucla.edu (Shinn-Tzong Wu) writes...J >> Hi, we just encounteded one of our worst nightmare, the VAXStation 3100I >> (running VMS 5.3) died probably because it ran out of disk space for   F >> the AUDIT process.  Since the AUDIT process tried to write into theK >> full disk in the process of rebooting, there seemed to be no way that we L >> can bring the system up.  We tried to boot it from a stand alone tape butP >> it won't access to any of the disks.  Can anyone suggest any help?  Thanks... > J >     Use a conversational boot to bring up a minimum system.  For a 3100,F >use B/1 at the `>>>' console prompt.  (If you have a console passwordI >enabled, you'll have to enter it in order to use any variant of the boot H >command other than just "B".)  From B/1, you'll get a `SYSBOOT>' prompt9 >where you can modify SYSGEN parameters; do the following  >SYSBOOT> SET STARTUP_P1 "MIN" >SYSBOOT> CONTINUEF >from there the system will boot normally, except that under a minimumF >system many things are suppressed, including the audit server.  (AlsoI >systartup_v5, the site-specific startup procedure, is suppressed, as are . >sylogin and login.com once the system is up.) > G >     Log in immediately as SYSTEM, use SET LOGIN/INTERACTIVE=1 to keep E >ordinary users out, and then purge, delete, or move files to recover F >sufficient disk space for normal operation.  Lastly, reset the system >parametersi >$ run sys$system:sysgen >SYSGEN> USE CURRENT >SYSGEN> SET STARTUP_P1 "" >SYSGEN> WRITE CURRENT
 >SYSGEN> EXITt >and then reboot.i >-H >     This kind of stuff should be covered in the "emergency procedures"D >section of the system manager's manual(s).  Followups redirected to >vmsnet.sysmgt.l >M% >		Pat Rankin, rankin@eql.caltech.edu7 > ? [Ed. note: The instructions to perform a minimum boot vary fromOD processor to processor.  The instructions here are specific to a VAXA 3100 (although most of the 3xxx product line seems to follow thisaG "standard") NOT to all VAXen.  Check the Installation Supplement manual C for your specific processor for the conversational boot procedure.]-E ---------------------------------------------------------------------  ,DIR  / >Subject: Why does emptying a dir take so long? * >From: qb7g6@fel.tno.nl (Maarten Landzaat) > ? >I'm sorry if this is a FAQ. I don't often read VMS newsgroups.t< >A friend of mine using VAXstations 3100 and 4000(?) running) >5.4 and 5.5 told me this striking story:o >cJ >He has a few directories containing a few hundred files. Sometimes, theseK >dirs need to be emptied. He then issues a simple delete *.*;* or whatever. G >then VMS takes an INCREDIBLE time of 2 hours (5.4) or 45 minutes (5.5)m >to delete the files.  >9C >Now I've been working with VMS and unix, and didn't find that manysF >performance differences. But this is a VERY big difference. I've seenA >lots of unix directories with hundreds of files, and delete time.E >seems linear. Deleting a few files on VMS does not take a long time,"4 >at least IMO. Is VMS file deletion then not linear? > 2 >Does anybody know why VMS takes such a long time?3 >Is it fundamental to the VMS filesystem structure?0  ) #From: ewilts@galaxy.gov.bc.ca (Ed Wilts)o # O #I would hazard a guess that the size of the directory file exceeds 127 blocks. N #The size of this file is proportional to the number of files in the directoryM #and the length of each file name.  I am surprised that you're seeing it withu #only a few hundred files. #tL #Once you hit this magical limit [127 blocks], all hell breaks loose and youD #wait forever to get any work done.  Spread your files over multiple #sub-directories if possible.0  4 #From: granoff@ranger.enet.dec.com (Mark H. Granoff) #oP #Try deleting the files in reverse alphabetical order.  It'll take a little moreP #code (DCL, for example) than a simple DELE *.*.* command, but it'll improve the' #performance of that logical operation.h #BO #Directory files are maintained in alphabetical order.  If you delete the firsthN #file in a directory, the directory file must be compressed and/or shuffled toO #remove that first entry.  In a directory containing many files, this will takee #some time.t   #From: dfilip@colornet.UUCPC # H #If all access to the directory becomes VERY SLOW (including DIR's) thenJ #I would suggest looking at the SYSGEN parameter ACP_DIRCACHE. This is theL #number of blocks of a directory file that are kept in cache. Although a fewL #hundred files should NOT create an extremely large directory, if there wereH #ever a lot more (i.e., thousands) then this could be your problem sinceI #directory files are not automatically compressed when files are deleted.t # I #ACP_DIRCACHE should be slightly larger than your largest directory file.dI #The parameter is dynamic, so you can change it without rebooting and seeb #if it fixes your problem.E ---------------------------------------------------------------------y ,SIGK >From: "Kevin Cole at Gallaudet U. Washington DC" <CADS_COLE@GALLUA.BITNET>g7 Subject: Automatic Signatures, Emblems and ">" a la EDT   M Several people have asked me about automatic emblems.  I'm not saying this isfN the best way to do things...  I'm just saying it's the way I do things.  Seems- to work OK for me.  Well, here's how I do it:       tH         1) Create a file with your particular emblem or signature in it.)            (I called mine SIGNATURE.TXT.)t      t5         2) Add the following lines in your LOGIN.COM:b>             $ DEFINE/NOLOG MAIL$EDIT    SYS$LOGIN:MAILEDIT.COMB             $ MAIL      :== MAIL/EDIT=(SEND,REPLY=EXTRACT,FORWARD)      cI         3) Cut out the following two files (MAILEDIT.COM and MAILEDT.INI)l      eO <Cut here>-------------------- MAILEDIT.COM -------------------------<Cut here>f $ SET TERM/NOBROADCAST1 $ DEFINE /USER SYS$INPUT 'F$TRNLNM("SYS$OUTPUT")'h" $ IF P1 .EQS. "" THEN GOTO NOINPUT6 $ EDIT /COMMAND=SYS$LOGIN:MAILEDT.INI/OUTPUT='P2' 'P1' $ SET TERM/BROADCAST $ EXIT	 $NOINPUT:o* $ EDIT /COMMAND=SYS$LOGIN:MAILEDT.INI 'P2' $ SET TERM/BROADCAST $ EXITO <Cut here>-----------------------------------------------------------<Cut here>:      a      eO <Cut here>-------------------- MAILEDT.INI --------------------------<Cut here>l SET CURSOR 0:20 
 SET SCREEN 80  SET WRAP 79r SET SEARCH BEGIN@ SET ENTITY WORD '^H^I^J^K^L^M !"#$%&''()*+,-./:;<=>?@[\]^_`{|}~' SET WORD NODELIMITER DEFINE KEY GOLD 14 AS "5SHL."h DEFINE KEY GOLD 15 AS "5SHR."w DEFINE KEY GOLD D AS "DATE." C; ER -L 32000(62ASC -2L) ER EXs INC SYS$LOGIN:SIGNATURE.TXTt F BEGu C; IDate sent: ^Z DATE ^M EX SET MODE CHANGEeO <Cut here>-----------------------------------------------------------<Cut here>       u      oN NOTE: Change the ^H^I^J^K^L^M to control characters in the SET ENTITY command.J       Change the ^Z to control-Z (but NOT the ^M) in the second last line.      a
 Explaination:n      rO The above does a bit more than what is asked for...  The reason I spawn insteadaM of using callable EDT or TPU is because I prefer to turn off broadcasts whileeH I'm editing, and because the COM file runs a non-standard INI file.  TheM special INI file is what adds the emblem/signature.  It also does a few other J handy things like adding the time the message was sent, and adding the ">"K character to the beginning of every old line in a reply.  (That's a trick IfK learned from someone on this list ages ago.)  The guts are in the last fivet lines.       M First we move to the end of the buffer (ER).  Backup one line (-L).  Insert aoJ ">" (62ASC) and go to previous line (-2L) 32000 times.  When we've finallyL added as many ">" as we can, go back to the end of the buffer (ER).  Add theN signature file. (INC SYS$LOGIN:SIGNATURE.TXT).  Go back to the top of the fileN (F BEG) and add the current time and date (IDate sent: ^Z DATE ^M EX).  Lastly2 give control back to the sender (SET MODE CHANGE).  E ---------------------------------------------------------------------b ,FLA" Subject:  No question is stupid...8 >From:     John McMahon - NASA GSFC ADFTO - 301-286-2045)           <FASTEDDY@DFTNIC.GSFC.NASA.GOV>2$ Date:     Thu, 3 Aug 89 12:18:10 EDT  ; (Commentary having very little to do with Vaxen follows...)e  0 Sample antagonistic response to novice question:A ***> RTFM! Page 7-7 in binder 8B, the version 4 doc set. Just setsB ***> bit 28 and you're done! And stop asking such silly questions,, ***> which are so easily answered, will you!  H It seems to me that usefulness of Info-Vax/Comp.Os.Vms is decreased whenN someone out on the net asks a question and is greeted with comments like thoseJ above.  To you the question may seem trivial...  However, it wasn't to the person posting.o  M First thing to keep in mind:  Even if it's in the manuals, the person may not(J be able to find it.  If you posted a question about "How do I increase theL maximum record size for DECnet I/O", I could easily answer RTFM.  But that'sL only because I found it once...  It took a couple of hours, several manuals,M and a little luck.  Some people aren't that lucky, and some don't have accessyN to full documentation sets.  Also, when was the last time you actually read anL index that pointed to exactly what you wanted the first time ?  Most indexesK imply that the user knows approximately what he/she is looking for first...yL What is a user to do when he/she doesn't know where to look ?  How about ask the Info-Vax gurus...   H Second thing to keep in mind:  Not everyone here is at the same level ofO experience.  Just because you are talented/knowledgeable you don't have to holdsN that over a novice who is lost in VMS.  Remember that at one point, all of theN gurus (including you) were novices.  How far would you have advanced if peopleN you asked for help from said "Read the manuals...  You ask silly questions..."' Probably not as far as you have gotten..      lF Third thing:  Behind each posting is a person.  The network creates anH 'artificial buffer' which keeps us separate enough that we forget.  JustN because it's e-mail doesn't meen you shouldn't be polite.  We are humans after* all...  We are supposed to be civilized...      VN Boiled down to a point:  Info-Vax is a technical discussion involving everyoneL from the Novice to Guru level.  Let's keep it polite and technical...  Don't# post personal editorial comments...R      b* (I know, I probably just violated that...)      :. Please direct comments to me (not the list)...O /-------------------------------------+---------------------------------------\nO | John "Fast Eddie" McMahon           |    Span: SDCDCL::FASTEDDY (Node 6.9)  |oO | Advanced Data Flow Technology Office|    Arpa: FASTEDDY@DFTNIC.GSFC.NASA.GOV| O | Code 630.4 - Building 28/W255       |  Bitnet: FASTEDDY@DFTBIT              |eO | NASA Goddard Space Flight Center    |GSFCmail: JMCMAHON                     |tO | Greenbelt, Maryland 20771           |   Phone: x6-2045                      |n  P -------------------------------------------------------------------------------- ,IMAGE-DUMP-ANALYSIS" >Subject: Analyzing a process dump& >From: mjensen@BBN.COM (Martin Jensen) >SI >    I've got an executable that runs with the /dump qualifier.  I expectlI >    that, on occasion, the process will crash.  (as a matter of fact, weaJ >    intentionally crash it if software detects an unrecoverable condition >    in the code). >dJ >    The problem is that the dump files are pretty useless.  'show  calls'J >    reports  only the module names - no routine names - and I've only gotJ >    access to universal symbols.  The program is compiled with the /debug# >    switch and linked with /trace.  >cI >    Ideally, I would like to be able use anal/proc/image=xxx against thewE >    dump from the normally linked executable - where xxx would be anbI >    image containing the full DST and GST.  The couple of options I haverG >    tried allow me to analyze the dump, but the symbol locations don't ' >    match properly between the images.l >t >    Any ideas???.  & >Subject: Re: Analyzing a process dump* >From: gjc@mitech.com (George J. Carrette) >o= >The trick people use is to LINK/DEBUG and then use a commandhD >procedure that calls VMS PATCH to change the image back to thinking >it was LINK/NODEBUG.m > F >That way you get all the symbols in the image without having it start >up in the debugger. >dD >You can get a SETDEBUG.C or NSETDEBUG.COM, or other various of that7 >from various places. Probably VMSNET.SOURCES archives.  >  >-gjcp  P -------------------------------------------------------------------------------- ,MCR) Subject: Response to Question about "MCR"l& >From: Bruce Wright <rti!bcw@MCNC.ORG>! Date: Thu, 28 Sep 89 15:31:08 GMT(  I In article <22331@cup.portal.com>, Wiley_M_Sanders@cup.portal.com writes:nI >    MCR stands for "Monitor Console/Control Routine", and is a vestigialuK > element left over when PDP-11 programs could be run under VMS. MCR is/wasyG > the RSX-11 equivalent of the RUN command, although it really RUNS the C > image as a foreign command, as opposed to RUN, which launches the-= > installed image. In that way it's not exactly a synonym for  > RUN SYS$SYSTEM.U      TG Sorry if this is too pedantic for the net.censors, if you don't like ite just hit the "n" key.t      tH The MCR command on VMS is more-or-less like RUN on VMS, though with someK of the slight differences that have been mentioned here and elsewhere - buthH MCR on RSX was NOT the RSX equivalent of RUN.  VMS doesn't have an exactG equivalent of MCR - the closest thing is DCL;  MCR was the user command C line interface module under RSX.  As noted, MCR stands for "Monitor 6 Console Routine" and was the prompt that the user saw:        	MCR>your-RSX-command=      EG RUN was a very respectable RSX command - it ran a user image as a task.(J RSX commands were one-to-three letter commands which were derived from theJ names of installed tasks (sort of like an installed image on VMS, but when< it was invoked it would start a new task [=process on VMS]).      OJ RSX commands were one-to-three letter commands which were derived from theH names of installed tasks.  These were run as separate tasks (=process onH VMS) when the corresponding command was entered (everything on RSX was aJ task, image activation corresponded to task activation).  Since there wereJ a number of different versions of RSX (RSX-11A, RSX-11B, RSX-11C, RSX-11D,F RSX-11M, RSX-11M+, RSX-11S, IAS, POS, and maybe others), some of whichD shared only a few architectural and historical things in common, theG precise details of the implementation differed somewhat between membersY of the family.      EK Later versions of RSX (and some of its derivatives such as IAS) did includesH a DCL interpreter which had numerous similarities (and differences) withH respect to VMS DCL.  Because of the architecture of the systems, many ofK the DCL commands in the RSX family would start a new task (=process) rathernI than run an image in the same process as on VMS - but the effect from thex$ user point of view was very similar.      rJ >    Alas, the MCR command interpreter seems to be absent from VMS 5.2. At5 > least when I type SPAWN/CLI=MCR, it can't be found.h      'J The MCR command is left over from when the RSX compatibility mode softwareK was bundled in with VMS.  Those of you that have been around since VMS V1.0aI probably remember that, for example, DIRECTORY was implemented as PIP /LIhJ and that many commands (including DIRECTORY) would spit out RSX-like errorI messages like "PIP -- No such file(s)".  It started out as much as an aidtK for DEC to get all that utility software running on the VAX as it did as ann% aid for helping customer conversions.t      oK Since at least V4.0 this has been separate product (VAX-11 RSX) which sitesgH with an earlier license automatically had a license to use.  When it wasJ made a separate product, all the RSX code (MCR, PIP, TKB, FLX, and all theI other friends from the RSX world, and BACKTRANS.EXE and other things from H the VMS world which made the whole mess work) were removed and made part of the VAX-11 RSX product.      FG When this was done, the MCR command was probably left in the DCL tablesFI because removing it would break too many command files and annoy too many H people who had gotten used to typing "MCR mumble" instead of the wordier "RUN SYS$SYTEM:mumble".p      g        						Bruce C. Wrightt --' Dick Munroe				Internet: munroe@dmc.come= Doyle Munroe Consultants, Inc.		UUCP: ...uunet!thehulk!munroeo% 267 Cox St.				Office: (508) 568-1618i& Hudson, Ma. USA				FAX: (508) 562-1133  J GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection.  