[ From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  2-AUG-1990 17:52:22.34  To:	MRGATE::"ARISIA::EVERHART" CC:	+ Subj:	Info-VAX Monthly Posting, Part 3 of 3   * Received:  by crdgw1.ge.com (5.57/GE 1.70)( 	 id AA25345; Thu, 2 Aug 90 17:27:32 EDTY Received: From UCBVAX.BERKELEY.EDU by CRVAX.SRI.COM with TCP; Thu,  2 AUG 90 12:22:47 PDT , Received: by ucbvax.Berkeley.EDU (5.63/1.42)) 	id AA20309; Thu, 2 Aug 90 12:09:04 -0700 9 Received: from USENET by ucbvax.Berkeley.EDU with netnews . 	for info-vax@kl.sri.com (info-vax@kl.sri.com); 	(contact usenet@ucbvax.Berkeley.EDU if you have questions)  Date: 2 Aug 90 13:20:49 GMT b From: swrinde!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!deimos.cis.ksu.edu!mccall!tp@ucsd.edu8 Organization: The McCall Pattern Co., Manhattan, KS, USA. Subject: Info-VAX Monthly Posting, Part 3 of 3& Message-Id: <3310.26b828b2@mccall.com># Sender: info-vax-request@kl.sri.com  To: info-vax@kl.sri.com   A [Last changed: 2-AUG-1990] [Not really, but I just took it over.]   '            The Info-VAX Monthly Posting '            ---------------------------- 1            PART 3 -- Advanced "Common Questions". >            (Coordinated by Terry Poot, written by many others)  N (Part 1 is an introduction to Info-VAX.  Part 2 is Beginner Common Questions.)  ' 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)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)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 ---------------------------------------------------------------------  ,SIGK >From: "Kevin Cole at Gallaudet U. Washington DC" <CADS_COLE@GALLUA.BITNET> 7 Subject: Automatic Signatures, Emblems and ">" a la EDT   M Several people have asked me about automatic emblems.  I'm not saying this is N 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:        H         1) Create a file with your particular emblem or signature in it.)            (I called mine SIGNATURE.TXT.)        5         2) Add the following lines in your LOGIN.COM: >             $ DEFINE/NOLOG MAIL$EDIT    SYS$LOGIN:MAILEDIT.COMB             $ MAIL      :== MAIL/EDIT=(SEND,REPLY=EXTRACT,FORWARD)       I         3) Cut out the following two files (MAILEDIT.COM and MAILEDT.INI)        O <Cut here>-------------------- MAILEDIT.COM -------------------------<Cut here>  $ SET TERM/NOBROADCAST1 $ DEFINE /USER SYS$INPUT 'F$TRNLNM("SYS$OUTPUT")' " $ IF P1 .EQS. "" THEN GOTO NOINPUT6 $ EDIT /COMMAND=SYS$LOGIN:MAILEDT.INI/OUTPUT='P2' 'P1' $ SET TERM/BROADCAST $ EXIT	 $NOINPUT: * $ EDIT /COMMAND=SYS$LOGIN:MAILEDT.INI 'P2' $ SET TERM/BROADCAST $ EXITO <Cut here>-----------------------------------------------------------<Cut here>               O <Cut here>-------------------- MAILEDT.INI --------------------------<Cut here>  SET CURSOR 0:20 
 SET SCREEN 80  SET WRAP 79  SET SEARCH BEGIN@ SET ENTITY WORD '^H^I^J^K^L^M !"#$%&''()*+,-./:;<=>?@[\]^_`{|}~' SET WORD NODELIMITER DEFINE KEY GOLD 14 AS "5SHL."  DEFINE KEY GOLD 15 AS "5SHR."  DEFINE KEY GOLD D AS "DATE." C; ER -L 32000(62ASC -2L) ER EX  INC SYS$LOGIN:SIGNATURE.TXT  F BEG  C; IDate sent: ^Z DATE ^M EX SET MODE CHANGEXO <Cut here>-----------------------------------------------------------<Cut here>"             nN 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.       
 Explaination:i       O 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 otherMJ 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 IKK learned from someone on this list ages ago.)  The guts are in the last five8 lines.      >M First we move to the end of the buffer (ER).  Backup one line (-L).  Insert aeJ ">" (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>r$ Date:     Thu, 3 Aug 89 12:18:10 EDT  ; (Commentary having very little to do with Vaxen follows...)t  0 Sample antagonistic response to novice question:A ***> RTFM! Page 7-7 in binder 8B, the version 4 doc set. Just setDB ***> 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.-  M First thing to keep in mind:  Even if it's in the manuals, the person may notcJ 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 accesseN 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...tL 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 holdkN 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.y       F 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...      lN 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...        * (I know, I probably just violated that...)      e. Please direct comments to me (not the list)...O /-------------------------------------+---------------------------------------\nO | John "Fast Eddie" McMahon           |    Span: SDCDCL::FASTEDDY (Node 6.9)  | O | Advanced Data Flow Technology Office|    Arpa: FASTEDDY@DFTNIC.GSFC.NASA.GOV|oO | Code 630.4 - Building 28/W255       |  Bitnet: FASTEDDY@DFTBIT              |yO | NASA Goddard Space Flight Center    |GSFCmail: JMCMAHON                     |RO | Greenbelt, Maryland 20771           |   Phone: x6-2045                      |n  E ---------------------------------------------------------------------i ,MCR) Subject: Response to Question about "MCR" & >From: Bruce Wright <rti!bcw@MCNC.ORG>! Date: Thu, 28 Sep 89 15:31:08 GMTi  I In article <22331@cup.portal.com>, Wiley_M_Sanders@cup.portal.com writes:hI >    MCR stands for "Monitor Console/Control Routine", and is a vestigialeK > element left over when PDP-11 programs could be run under VMS. MCR is/wasbG > the RSX-11 equivalent of the RUN command, although it really RUNS therC > image as a foreign command, as opposed to RUN, which launches thea= > installed image. In that way it's not exactly a synonym ford > RUN SYS$SYSTEM.       sG Sorry if this is too pedantic for the net.censors, if you don't like itr just hit the "n" key.-       H 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 - but H 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 commandtC line interface module under RSX.  As noted, MCR stands for "Monitore6 Console Routine" and was the prompt that the user saw:        	MCR>your-RSX-command        G RUN was a very respectable RSX command - it ran a user image as a task.yJ 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]).      fJ 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 members- of the family.      -K Later versions of RSX (and some of its derivatives such as IAS) did includeLH 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) rather I than run an image in the same process as on VMS - but the effect from theC$ user point of view was very similar.      iJ >    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.       EJ 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.0iI probably remember that, for example, DIRECTORY was implemented as PIP /LI-J 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 aid"K for DEC to get all that utility software running on the VAX as it did as an % aid for helping customer conversions.       /K Since at least V4.0 this has been separate product (VAX-11 RSX) which sites-H 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 fromHH the VMS world which made the whole mess work) were removed and made part of the VAX-11 RSX product.      LG When this was done, the MCR command was probably left in the DCL tablesAI 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".-      -      - 						Bruce C. Wright   