[ From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  2-AUG-1990 19:24:05.15  To:	MRGATE::"ARISIA::EVERHART" CC:	+ Subj:	Info-VAX Monthly Posting, Part 2 of 3   * Received:  by crdgw1.ge.com (5.57/GE 1.70)( 	 id AA28987; Thu, 2 Aug 90 19:11:39 EDTY Received: From UCBVAX.BERKELEY.EDU by CRVAX.SRI.COM with TCP; Thu,  2 AUG 90 12:23:02 PDT , Received: by ucbvax.Berkeley.EDU (5.63/1.42)) 	id AA20290; Thu, 2 Aug 90 12:08:39 -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:32 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 2 of 3& Message-Id: <3309.26b828a0@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.]  [ Changes since last month: F           (1) Added:  Why doesn't my program work when RUN/DETATCH'ed?+           (2) Updated: Linking and VAX C. ]   '            The Info-VAX Monthly Posting '            ---------------------------- 1            PART 2 -- Beginner "Common Questions". >            (Coordinated by Terry Poot, written by many others)  N (Part 1 is an introduction to Info-VAX.  Part 3 is Advanced Common Questions.)  ' Save this message for future reference!    Table of Contents:  L ,GEN   -- General beginner questions (the Top 7 quickies) updated 1989-10-03           Many, many authorsL ,RDT   -- Why doesn't my program work when RUN/DETATCH'ed?  added 1990-01-31,           sommar@enea.se (Erland Sommarskog)5           Leichter-Jerry@cs.yale.edu (Jerry Leichter) L ,LIC   -- Linking and VAX C                               updated 1989-01-064           pjt@yin.cpac.washington.edu (Larry Setlow).           TAYLORT@decus.com.au (Trevor Taylor)L ,TIM   -- Why does VMS time start at November 17, 1858    updated 1989-08-285           billy@vaxb.acs.unt.edu (Billy Barron & DEC) L ,VAC   -- The VAX Vacuum cleaner                            added 1989-12-28:           schuette@acoustics.nrl.navy.mil (Larry Schuette)3       and KLENSIN@infoods.mit.edu (John C. Klensin) L ,MAI   -- Mail tips                                         added 1989-09-29.           CADS_COLE@GALLUA.BITNET (Kevin Cole)L ,QU1   -- Disk quotas                                     updated 1989-09-02&           Rollo.Ross@levels.sait.oz.auL ,QU2   -- Diskquota Discrepency                           updated 1989-09-02/           R602MS5U@vb.cc.cmu.edu (Marc Shannon) M [There are two articles on disk quota because I couldn't decide which to use. N If someone would like to edit them into one article and submit it, fine. -TAL]L ,CPD   -- How to copy an entire directory structure       updated 1989-08-03+           bfoss@goofy.apple.com (Brad Foss)   D (the ",REQ", ",GEN", etc. are keywords.  If you search for that textJ (including the ",") you will be brought to the beginning of that article.)  E ---------------------------------------------------------------------  ,GEN1 General questions answered (from various sources)   * 1.  Where can I get old Info-VAX messages?  K The archives are held at SRI.COM (128.18.10.1), in files with obvious names K like "info-vax.txt.1".  Ramon Curiel <RAY@CRVAX.SRI.COM> does the thankless & job of maintaining them.  (Yea Ramon!)  D In the UK, archives are accessible via a mail server.  People shouldA send a message, with EITHER the subject field OR the message body H containing HELP, to info-vax-request@Uk.Ac.Ulcc.Ncdlab (addresses in theG UK are the opposite way round from the rest of the worlds ...  sigh...) $ The server will tell you what to do.  C Two years worth of Info-VAX messages are stored at VTVM2 which is a F Bitnet redistribution point.  If you have an account there, it is best= to use the database searcher.  Otherwise send the commands to F LISTSERV@VTVM2 using TELL (on an IBM system) or SEND (on a VMS system)C or "netwrite" (on a Unix system with the UREP software).  Send HELP F and INFO commands to get started.  A sample command is something like:F "$ SEND LISTSERV@VTVM2 SEND INFO-VAX LOG8901B" which will get you someD of the messages from Jan 1989.  You can also use INDEX to get a list of the Info-VAX files archived.   * [Any more places?  Please tell me!  -TAL ]  > 2.  How do I reset my new mail count when it gets out of sync?? In other words, what do I do when it says, "You have 1 new mail  message" but I really don't?  D Simple: Send yourself a mail message OR have someone else mail you aC message.  If you are in MAIL, exit and re-enter mail.  At the MAIL> > prompt, type READ/NEW until it tells you that there are no newC messages.  Then enter READ/NEW one more time.  Everything is fixed.    3.  What is the plural of VAX?  H VAXen, VAXln, VAXlen, VAXs, VAXes and just about everything else you canL imagine.  It's been discussed on the net many times and there has never been< a conclusion.  Therefore, you may call it anything you want.  J 4.  Where do I get VI, Kermit, (X,Y,Z)Modem, UUCP, ANU news, GNU software, LZW/Compress/Decompress ?   . See the monthly "Where do I get xxx?" posting.   5.  What's DECUS?   > There is a separate monthly posting about DECUS.  Look for it.  H 6.   What do you do about "undeliverable mail" messages that bounce back> to you from various sites when you post a message to Info-VAX?       K If the reason is "MTA congestion" just delete them.  If the reason is a bad K address, contact the postmaster at the destination site, suggesting that he E request that the addressee be removed from the Info-VAX mailing list.   F 7.  How can I submit a correction or addition to this monthly posting?  E Check out the signature for addresses.  Additions are always welcome, G corrections are prefered to be in VMS DIFF format if they are specific. I Unix DIFF format isn't as human-readable and almost never matches up with  the text I have stored here.  E ---------------------------------------------------------------------  ,RDT" Date: Tue, 2 Jan 90 22:53:30 +0100+ >From: "Erland Sommarskog" <sommar@enea.se> 9 Subject: Why doesn't my program work when RUN/DETATCH'ed?   B      A question that seem to be fairly common goes like this:  "WeB have program that runs as a detached process and tries to create aC subprocess with LIB$Spawn but always fail.  When we run the program % in the debugger everything works OK."   C      The answer to this one is when you run a program in a detached C process there is no command line interpreter (CLI) - e.g. DCL - and E since LIB$Spawn is a callback to the CLI it can't but fail.  The same K applies to other callback routines like LIB$Set_logical and LIB$Set_symbol.   8 The solution is simple.  Instead of starting the program# with RUN/DETACH Prog you should do:   5         RUN/DETACH SYS$SYSTEM:LOGINOUT/INPUT=PROG.COM * where PROG.COM contains the line RUN PROG.  ! >From: Leichter-Jerry@cs.yale.edu  Date: Wed, 31 Jan 90 12:51 EST  F [What Erland said is] basically correct, but there is one tricky thingG that it's important to watch out for:  The names you use for /INPUT and E /OUTPUT and /ERROR on RUN/DET (you would normally define all three so C that you could see what happened) are passed to the created process D UNTRANSLATED.  The new process will use them to define its values of@ SYS$INPUT, SYS$OUTPUT, and SYS$ERROR.  At the point that the newD process does that, the names must be valid.  Hence, the only logical. names you can use are those known system-wide.  G You can use $CREPRC in place of LIB$SPAWN if you don't need LIB$SPAWN's ' ability to pass logical names and such.  							-- Jerry   E ---------------------------------------------------------------------  ,LIC Subject: Linking and VAX C1 >From: Larry Setlow <pjt@yin.cpac.washington.edu> " Date: Fri, 8 Sep 89 10:35:48 -0700  9 A recent posting (maybe you saw it) reminds me of another A frequently-asked question:  "How come we have to have the vaxcrtl & explicitly added to the LINK command?"  A I'm not sure I know the whole answer, other than "the C library'sOF names are too likely to conflict with user-named routines, so we can'tE do it automatically without pissing a lot of people off, and we don'toF like C very much, anyway, so nyah." but I know it's been covered a few
 times before.L   Larry   A [ Note from the editor:  Trevor Taylor <TAYLORT@decus.com.au> hasbG pointed out some other information which encouraged me to write this: ]   C If you explicitly link with that library you'll get an old library.aF It's better to link to the sharable library, then you'll aways get the newest library.t  E This is not documented in the HELP file (try HELP CC LINK for the old.G method), just the VAX C manual that I have.  The manual doesn't mentioni? the dangers of the first method but does mention that using the E sharable library saves disk space and makes your program load faster.eL One program I use was 154 blocks, with the shareable library it is 5 blocks.  = You must use the shareable image if you want to have the mostiD up-to-date library.  The only way is to use an options file.  Create+ a file called VAXC.OPT containing the line:n   	SYS$LIBRARY:VAXCRTL/SHARE   Then link as follows:o   	$ LINK myprog,VAXC/OPT-  E ---------------------------------------------------------------------  ,TIML [ DEC wrote it, Billy Barron <billy@vaxb.acs.unt.edu> submitted it, I editedM it down (it included a complete history of time telling and calendars) -TAL ]g  E COMPONENT:  SYSTEM TIME                  OP/SYS:     VMS, Version 4.nn  # LAST TECHNICAL REVIEW:  06-APR-1988e  2 SOURCE:   Customer Support Center/Colorado Springs  H QUESTION: Why is Wednesday, November 17, 1858 the base time for VAX/VMS?  J ANSWER:   November 17, 1858 is the base of the Modified Julian Day system.  K The Modified Julian Day was adopted by the Smithsonian Astrophysical Obser-e, vatory (SAO) in 1957 for satellite tracking.  J Eighteen bits would allow the Modified Julian Day (the SAO day) to grow asH large as 262,143 ((2 ** 18) - 1).  From Nov.  17, 1858, this allowed forJ seven centuries.  Using only 17 bits, the date could possibly grow only asK large as 131,071, but this still covers 3 centuries, as well as leaving thesF possibility of representing negative time.  The year 1858 preceded theL oldest star catalog in use at SAO, which also avoided having to use negative3 time in any of the satellite tracking calculations.K  I This base time of Nov.  17, 1858 has since been used by TOPS-10, TOPS-20, B and VAX/VMS.  Given this base date, the 100 nanosecond granularityL implemented within VAX/VMS, and the 63-bit absolute time representation (theD sign bit must be clear), VMS should have no trouble with time until:      s    31-JUL-31086 02:48:05.47u      fD At this time, all clocks and time-keeping operations within VMS will1 suddenly stop, as system time values go negative.t       E Note that all time display and manipulation routines within VMS allow J for only 4 digits within the 'YEAR' field.  We expect this to be corrected= in a future release of VAX/VMS sometime prior to 31-DEC-9999.t  E ---------------------------------------------------------------------- ,VAC Date: 26 Dec 89 09:49:00 EDT9 >From: "Larry Schuette" <schuette@acoustics.nrl.navy.mil>o Subject: VAX vacuum   > 	The VAX vacuum has been available in the U.K. long before DECL ever thought of building a 32bit processor.  When DEC did a trademark searchM they only checked the U.S. (or at least not the U.K).  Much to their chagrin,sO DEC discovered (too late) that VAX was already a licensed trademark in the U.K.iJ A deal was struck, and because the products are not similar, life goes on.C 	However, DEC would be in trouble should the vacuum cleaner companyf- decide to make "computers that suck" as well.lC 	The best part of this story is that, every few years, a new eager tJ Digital lawyer will "discover" that some British company has "stolen" the K VAX trademark.  Typically, in an effort to impress the boss, they will fire M off letters threatening legal action unless some license (read money) is senteN DEC's way.  The lawyer is then shot down in flames when the same standard form letter is sent from the U.K.   Larrys  0 [ Thanks, Larry.  I also got a note from John C.= Klensin <KLENSIN@infoods.mit.edu> on Thu, 28 Dec 1989 asking:8  G >     If there is really any interest in this, the term apparently also D >  means something (non-computer) in Sweden.  When I was last there,C >  I saw "VAX" plastered in large letters on the outside of severaloE >  buildings out in the sticks along highways.  I never got around toiE >  asking what they were associated with, but the buildings tended tosA >  be surrounded by heavy machinery, of the road-grading variety.rD >    I can pursue this if you like, otherwise will leave well enough	 >  alone.e >     John Klensin >     Klensin@INFOODS.MIT.EDU   3 [ Ok Info-VAXers, any answers?  Them to me.  -TAL ]   E ---------------------------------------------------------------------i ,MAIK >From: "Kevin Cole at Gallaudet U. Washington DC" <CADS_COLE@GALLUA.BITNET>o Subject: Mail tips  L [Some of these symbols may conflict with those in the ,SIGS posting, but the! information is still good.  -TAL]   L To tell MAIL to use an editor, include the following line in your LOGIN.COM:      a:         $ MAIL  :== MAIL/EDIT=(SEND,REPLY=EXTRACT,FORWARD)      oK (Remove the "=EXTRACT" from the above line if you do not want the text fromiJ old messages to be included in replies and forwarded messages.)  MAIL willM default to CALLABLE_EDT as it's choice of editor.  If you would prefer to usep6 EVE/TPU, put the folllowing in your LOGIN.COM as well:       4         $ DEFINE/NOLOG MAIL$EDIT        CALLABLE_TPU       O Another option is to have MAIL spawn a seperate process for editing.  You mightcM wish to do this if you have a COM file which you want executed every time you M use MAIL.  For example, I have one which turns off broadcasts before startingiN the editor so that I do not get interrupted while sending mail.  In that case,H just define the logical MAIL$EDIT to point to your COM file instead of a callable editor.  Like so:      2>         $ DEFINE/NOLOG MAIL$EDIT        SYS$LOGIN:MAILEDIT.COM      yO Finally, if you wish to redefine the numeric keypad functions while within mail H you can create a file (say, for example MAIL.INI) which contains the new definitions:      r>         DEFINE/KEY PF2                "SHOW KEY/ALL"/TERMINATEI         DEFINE/KEY PF2/IF_STATE=GOLD  "SHOW KEY/ALL/STATE=GOLD"/TERMINATEt9         DEFINE/KEY PF3                "EXTRACT"/TERMINATEhN         DEFINE/KEY PF4                "IN%"""INFO-VAX@KL.SRI.COM""""/TERMINATE8         DEFINE/KEY PERIOD             "DELETE"/TERMINATE2         DEFINE/KEY ENTER              ""/TERMINATE      eO And add a line in your LOGIN.COM which points the logical MAIL$INIT at the fileD      r:         $ DEFINE/NOLOG MAIL$INIT        SYS$LOGIN:MAIL.INI  E ---------------------------------------------------------------------i ,QU1# >From: Rollo.Ross@levels.sait.oz.au  Subject: Diskquotas  Date: Sat, 2 Sep 89 22:52 +0930,  J          Users often complain that their disk usage as shown by SHOW QUOTAK doesn't match the total size of their files. Here are some reasons why this  happens:  H 1) Every file consists of at least one 1-block header and some number ofG clusters, which are usually 3 blocks long. You may have only 1 block offK data, but you have removed 4 blocks from the space available to others, ando> your quota shows 4 blocks gone. To see the effect of this, use"         $ DIR [...]/SIZE=ALL/GRANDK The "SIZE=ALL" shows both the space used and the number of blocks allocatedWK to the file. It does not show the 1 block header for each file, but you can-K see how much this adds up to by looking at the count of files shown. So, ifLN you add together the LARGER of the two sizes shown in the grand total given byK the command above, and the total number of files, you have a better idea of , the total number of blocks allocated to you.  H 2) You may have files owned by you but stored in other directories. YourK own top-level directory is an example - it is is a xxxxx.DIR file stored inoK the directory "above" where you log in. You can check the size of that filel& using  the command DIR/SIZE=ALL/BY [-]  F 3) The quota file is sometimes inaccurate. For example, it may not getF updated if the system crashes just after you increase or decrease yourI usage. Bugs in VMS on a cluster also cause the quota file to drift out ofhM touch with reality.  Your system manager may need to do some disk maintenanceuI (ANALYZE/DISK/REPAIR dev) to fix this problem.  Check with him/her to see  if this is the case.  H         So, your problem is probably partly misunderstanding of how yourJ disk  quota works (items 1 and 2 above), possibly confused by a bug in the system (item 3).   Rollo Ross, Network Manager N Comp Centre,  Sth Aust Institute of Technology, The Levels, SA 5095, AustraliaN Voice: +61 8 343 3158                 Old way:  Rollo.Ross@levels.sait.oz{.au}N Fax: 349 6939      DTE 505282622004       Standard way: Rollo.Ross@sait.edu.au  E ---------------------------------------------------------------------e ,QU2 Subject: Diskquota Discrepency, >From: Marc Shannon <R602MS5U@vb.cc.cmu.edu> Date: Sat,  2 Sep 89 16:35:58y      XH      The SHOW QUOTA returns the number of blocks you have allocated overH the entire disk.  Presuming that all of your files are in your directoryF tree, use the DIRECTORY/SIZE=ALLOC/GRAND [...] command (from your home5 directory) to see just how many blocks you are using.   D      Note the "/SIZE=ALLOC" qualifier; this has DIRECTORY report theH number of blocks which each file is *allocated*, not just in actual use.D (Most systems have a "cluster-size" of 3 which means that every fileH must take up a multiple of 3 blocks, so even files with one line in them take up 3 blocks.)  D      Okay, now you're getting close, but VMS still charges you a bitG more.  For every file you own, you are also charged 1 block so that VMSiF can store information in the INDEXF.SYS file on your disk about how toH find your file.  So, take your total number of blocks and add the number6 of files and directories found in your directory tree.  D        Now you should be almost at the number reached by SHOW QUOTA.H Don't forget your main directory.  Use DIR/SIZE=ALLOC [-]username.DIR toF see how large your main directory file is and add that (plus 1 for its INDEXF entry) to your total.      a:        This final total should be what SHOW QUOTA returns.      d --Marc  E ---------------------------------------------------------------------a ,CPDIR( >From: bfoss@goofy.apple.com (Brad Foss)& Subject: Copy-Directory to Remote Host! Organization: Network Innovationsa	 Lines: 26l  K >    Does anyone know why DECNET doesn't support the copying of directories G > with unknown sub-directory structure?  Right now, to copy a directory F > between 2 vaxes I must login to the destination host, create all theI > sub-directories required in the destiation directory and use individualRJ > copy commands to pull the files from each source host sub-directory into > the destination directory.  L I've had occasion to move directory structures, even whole disks to a remoteE node.  The only way I've succeeded at it is to use BACKUP to create acE saveset on the remote host, then log in to the remote host and backupl6 (restore) the saveset to the desired disk.  Like this;       (at local host)WB $ BACKUP/LOG DISK:[DIR...]*.*;* REMOTE::DISK:[DIR]SAVESET.BCK/SAVE   ( at remote host)c3 $ BACKUP/LOG DISK:[DIR]SAVESET.BCK/SAVE DISK:[*...]V  L You said any help would be appreciated, and this sure beats having to createK directories and use COPY.  BACKUP will create the directories as needed.  IlI expect others will suggest that you create the saveset on the local host,aI then DECnet it to the remote host.  It seems to run a little quicker thatr way.  