Path: utzoo!utgpu!watmath!att!dptg!rutgers!cs.utexas.edu!swrinde!ucsd!ucbvax!UMINN1.BITNET!IJIM
From: IJIM@UMINN1.BITNET (Jim Colten)
Newsgroups: comp.lang.asm370
Subject: Re: GETFST
Message-ID: <8909211637.AA16566@jade.berkeley.edu>
Date: 21 Sep 89 14:30:53 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.bitnet@jade.berkeley.edu>
Distribution: inet
Organization: The Internet
Lines: 20

>Jim,
>
>I did neglect to say that on the mainframe the date/time stamp is
>changed by a disconnected vm. Users are not permitted to change their
>own files.
>

That is marginally better.  A file has a timestamp and I feel that the one
and only valid timestamp is the one that indicates when the data in the file
was last changed.  Besides, when viewed from a low enough level, the DVM is
indeed a user :-)

The previous posting on this topic suggested a valid use for correcting the
timestamp of a file that had been transfered from another machine without
the timestamp being preserved.  That seems ok as a cure.  Apply the cure and
continue to press for prevention (the file xfer software could preserve the
timestamp).

cheers,
Jim