No matter what system you happen to be on, when you display the creation
date/time for a file, you expect it to be a constant that reflects the
actual creation date/time.  Copy semantics should always preserve this
constant quality to avoid the "surprise" factor.

And even if an ftp is a "foreign" file that did not previously exist on the
target system, the data in that file has characteristics that should be
preserved.  Creation date/time is just one of those characteristics.  Just
because the file is "new" for the target system does not mean the data
itself is new.

Peter

-----Original Message-----
From: Perryman, Brian [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 14, 2005 4:32 AM
To: [email protected]
Subject: Re: Setting the Creation Date for datasets


Charles

That would seem a reasonable expectation at first, but with various systems'
copy commands you are of course dealing with the same environment, including
timezones.

If you try and extend this to FTP, then you get into the realms of trying to
determine whether the source file was GMT stamped or GMT/offset/local-time
stamped and by how much, and what time do you therefore put on it.

Also there's the concept that with copy commands the file already existed on
the source (and target) environment; with FTP, by nature it's a 'foreign'
file which didn't previously exist on teh target system. It's therefore a
new creation at the time it was sent.

Brian

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of Charles Mills
Sent: 14 June 2005 00:49
To: [email protected]
Subject: Re: Setting the Creation Date for datasets


Gil, what about the cp command on Solaris - what does it do?

Wouldn't the least astonishing behavior for FTP be to behave as copy and
cp do?

Charles

_
This message and any attachments are intended only for the use of the addressee 
and
may contain information that is privileged and confidential. If the reader of 
the 
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to