Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uunet!peregrine!ccicpg!felix!hplabs!ucbvax!UHRCC2.BITNET!NSMCC
From: NSMCC@UHRCC2.BITNET (Howard Jares, CRCC Mgr 713-749-4612)
Newsgroups: comp.os.vms
Subject: VMS terminal port errors and Expir dates on dirs rather than volume
Message-ID: <8706122241.AA27219@ucbvax.Berkeley.EDU>
Date: Thu, 11-Jun-87 10:59:00 EDT
Article-I.D.: ucbvax.8706122241.AA27219
Posted: Thu Jun 11 10:59:00 1987
Date-Received: Sun, 21-Jun-87 01:15:29 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 19

Hello,
  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.
  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...

Howard Jares, Manager                 Cannata Research Computation Center
NSMCC@UHRCC2 (BITNET)                 University of Houston
CRCC::HOWARD (TEXNET)                 4800 Calhoun SR1 Rm 221D
713-749-4612 (MABELL)                 Houston, Tx 77004