In a recent note, TISLER Zaromil said: > Date: Tue, 14 Jun 2005 12:57:39 +0200 > > - PDS(E) member level: > old copy creation date&time = new copy creation date&time > > In the second case it looks like someone found it to be important to > propagate the original creation and change date & time (XMIT does it between > systems). > This may be true if you TRANSMIT in IEBCOPY format, but only because IEBCOPY, not TRANSMIT, preserves the directory entry.
But I just tried TRANSMITting a PDS member with time information with the SEQ option. The only time I saw when I browsed the spool with SDSF was the time of transmitting, not the ISPF timestamp, and when I RECEIVEd it, the timestamps are all blank in a DSLIST MEMBER display. I strongly agree with Charles, member timestamps need to be made consistent, across all products, best done by moving the code from ISPF to STOW itself. As I've said, it's one of my reasons for preferring the "radically immature" HFS (which nonetheless does it right) over PDS. The transition from PDS to PDSE would have been a logical point at which the OS could have begun maintaining member timestamps. Somehow, IBM missed that one. -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- 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
