The uncatalog operation does not occur until the file is actually scratched. So, while it is at the WAIT vault it will still be cataloged.
However, you could use our TMSUNCAT utility and pass it the list of files at the WAIT vault. It does get more tricky, since the vaulting system will only look at file-1 and the TMSUNCAT needs to be passed all the files that need to be uncataloged. So it could be done, but normally we will not un-catalog the files until they are scratched. Russell Witt CA 1 L2 Support Manager -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu]on Behalf Of Vernooij, CP - SPLXM Sent: Wednesday, January 13, 2010 8:43 AM To: IBM-MAIN@bama.ua.edu Subject: FW: Prod datasets VAULTing na expiration Russel, One additional question: does CA-1 uncatalog the tapes when their expiration date has come and they are moved to the WAIT vault? If so, they look the same as SMS datasets: the seem to be gone, but a backup is still available for exceptional cases. If they remain cataloged, the user can still see them and might complain about paying for tapes, that he does not need anymore. Kees. -----Original Message----- From: Vernooij, CP - SPLXM Sent: woensdag 13 januari 2010 13:46 To: 'IBM-MAIN@bama.ua.edu' Subject: Re: Replace VTS with a tape less appliance Russel, Thanks, that is an excellent approach. This way I can apply it selectively to those tapes that need it and let the rest expire and scratch immediately when their retpd is reached. Kees. "Russell Witt" <res09...@verizon.net> wrote in message news:<hmeajbgcfmbdcgnlppgjoekjcoaa.res09...@verizon.net>... > Kees, > > That is correct, there is no option within CA 1 to extend the expiration > date of files maintained by RETPD= in the JCL or RDS file. > > However, you could get "tricky" with the vaulting system. For example, some > clients treat their robotic environment as their only library (no manual > drives) and everything on the shelf (even within the data center) is > considered a pseudo-vault. So, their vaulting rules basically say "keep > inside the library (robot) until un-referenced for 15 days; then move to > vault SHLF until expired". You could then simply add a third rule that says > "then move to vault WAIT for 7 days". Until the tape is released from > location WAIT (even though it is expired) it will not be eligible to be > scratched. > > This does mean that every tape in your library would be assigned to some > vault location, but you could "vault" the tape to HOME until expired; and > then move to WAIT for 7 days. This would delay the scratching of tapes until > 7 days AFTER it has expired. But, once the tape is scratched it is > scratched. > > Russell Witt > CA 1 L2 Support Manager > > ............................... > Russel, > So this does not delay scratching a tape that has its expiration date > from the RETPD= parameter in JCL or RDS? > I have a number of candidates for disk-tape conversion (reversing the > tape-disk conversion of 10-20 years ago). But the drawback is that we > loose the 'retain days only backup dataset deleted' feature of SMS. Once > the dataset is expired, the tape can be overwritten and there is no way > back anymore. I was planning to check if CA-1 has something similar, but > apparently not for every tape. > > > Kees. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html ********************************************************************** 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 lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
