Kees, DSS DUMP read tracks and recoveres the VTOC as a file, I believe.
Itschak On Tue, Apr 7, 2009 at 10:01 AM, Vernooy, C.P. - SPLXM <[email protected] > wrote: > > > > 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 > > > >"Itschak Mugzach" <[email protected]> wrote in message > news:<[email protected]>... > > 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 > > > > No, remember the OP is copying datasets from tape to disk. After the > copy, the dataset has today as creation date. A physical backup and > restore does not change this. He likes to change the creation date back > to the original creation date of the dataset on tape. > > Kees. > ********************************************************************** > For information, services and offers, please visit our web site: > http://www.klm.com. This e-mail and any attachment may contain > confidential and privileged material intended for the addressee > only. If you are not the addressee, you are notified that no part > of the e-mail or any attachment may be disclosed, copied or > distributed, and that any other action related to this e-mail or > attachment is strictly prohibited, and may be unlawful. If you have > received this e-mail by error, please notify the sender immediately > by return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries > and/or its employees shall not be liable for the incorrect or > incomplete transmission of this e-mail or any attachments, nor > responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal > Dutch Airlines) is registered in Amstelveen, The Netherlands, with > registered number 33014286 > ********************************************************************** > > ---------------------------------------------------------------------- > 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
