Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!cica!tut.cis.ohio-state.edu!ucbvax!@rice.edu:IJIM@UMINN1.BITNET
From: @rice.edu:IJIM@UMINN1.BITNET (Jim Colten)
Newsgroups: comp.lang.asm370
Subject: Re: GETFST
Message-ID: <8909090302.AA23015@brazos.rice.edu>
Date: 8 Sep 89 18:03:16 GMT
Reply-To: IBM 370 Assembly Programming Discussion List <@rice.edu:ASM370%UCF1VM.BITNET@ricevm1.rice.edu>
Distribution: inet
Organization: The Internet
Lines: 18

>Jim, I disagree with you. I just recently wrote a program to change
>the date/time stamp on CMS files. I come from a large Engineering shop
>where the NC data on PC's are uploaded to the mainframe  but due to the
>nature of the upload facility the original dates are not retained. In order
>to keep the data matched on both sides we make sure that the dates are
>correct on the PC as well as the mainframe.
>

Well, I asked for it, didn't I.

I will, with some reluctance, agree that your requirement for changing a file's
timestamp is reasonable and valid.  Actually I have no quarrel with your
requirement.  After all, its purpose is to allow you to preserve the file's
'real' timestamp.  The reluctance comes from the fact that the tool is present
and available for uses where the timestamp ought not be changed.

Perhaps you could convince your file transfer software vendor to add the
timestamp preservation feature to the product?