Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU.UUCP
Newsgroups: comp.os.vms
Subject: Re: VMS terminal port errors and Expir dates on dirs rather than volume
Message-ID: <870613144645.05p@CitHex.Caltech.Edu>
Date: Sat, 13-Jun-87 17:49:33 EDT
Article-I.D.: CitHex.870613144645.05p
Posted: Sat Jun 13 17:49:33 1987
Date-Received: Mon, 15-Jun-87 03:39:56 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 33


 >   Does anyone know what VMS counts as a error on a DMF32 or  a  DHU11?   On
 > one of my systems I have begun seeing some errors but naturally they aren't
 > logged in the error log.  I have been trying to get my communication guy to
 > track down the problems but he hasn't been able to.

Try checking for unterminated terminal lines.  These can echo garbage back  at
the  DMF32  or DHU11, and I have reason to believe that such garbage generates
errors.

 >   The set volume expiration date feature works nice when you want to  apply
 > it  to  a  entire volume.  Unfortunately, me and my system guys get to work
 > only on the system disk.  I would  like  to  use  the  expiration  date  in
 > conjunction  with backup to archive old work.  The question I have is:  Can
 > I selectively turn on the expiration date  (to  be  automatically  modified
 > when  accessed)  only on a complete directory tree?  I realize that I could
 > do this by doing the set volume/expire but this will  be  updating  all  my
 > system  file  headers  as  the  system is used.  I would like to avoid this
 > overhead.  My gut feeling is that I get to wait for VMS V5...

What I've done on my system is to set the expiration date on all files in  the
system directory tree to a date far enough in the future that this field won't
need to be updated until a new version of VMS is installed.  This  should  cut
down  the  overhead  substantially.   Since  you're  interested  in  using the
expiration date for an archiving system, there's no need to make  the  minimum
and  maximum  retention  periods to nearly the same value.  On my system, they
differ by a day, which is much more precision than is really needed; thus  the
header of any file has the expiration date updated no more than once a day.

Arpanet:	CARL@CITHEX.CALTECH.EDU			Carl J Lydick
Bitnet:		CARL@CITHEX.BITNET			356-48 Caltech
HEPNet/SPAN:	CITHEX::CARL				Pasadena, CA 91125
							(818) 356-6660