The kind of backup you refer to is based on the change bit (Which is reset on restore). DMS Vtoc utility is a dataset by dataset update utility. a physical backup &restore would solve the need to "zap" the vto and would keep the original creation dates.
Itschak On Tue, Apr 7, 2009 at 3:03 AM, Paul Gilmartin <[email protected]> wrote: > On Mon, 6 Apr 2009 15:43:20 +0300, G+D+J+ B+N% #B+J+ <[email protected]> > wrote: > > >We are in the process of copying datasets from tape to disk. The users > would like to keep the same creation dates. > > > How is changing the date likely to influence the backup > process? If a backed up version with the same DSNAME > and a more recent timestamp exists, might the backup be > skipped? > > Likewise, I noticed (long ago; it may now be different) > that when I restored a data set from a backup copy, > it was given the timestamp of the time of the restore. > This would seem to cause HSM to back up the data set > needlessly at the next cycle. > > I suppose there are different timestamps in many places; > it all depends on which one the backup utility honors. > > -- gil > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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
