You have to accept the fact that you are going to lose some data. The Force parameter will allow you to recycle whatever data is readable onto another tape. Whatever is not readable is gone. You allowed migrated data apparently without having alternate tapes. Lost data due to a bad tape is the risk you took.
-----Original Message----- From: willie bunter [mailto:williebun...@yahoo.com] Sent: Tuesday, August 28, 2012 7:29 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: QUESTION ON HSM ; BYPASSING DSNS ON A ML2 TAPE By using FORCE would I lose the tape? I remember once before I did that and I think it got deleted from HSM. ________________________________ From: "Staller, Allan" <allan.stal...@kbmg.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, 28 August 2012 1:10 PM Subject: Re: QUESTION ON HSM ; BYPASSING DSNS ON A ML2 TAPE HSEND RECYCLE EXECUTE VOL(xxxxxx) FORCE ? What you have described is usually successful. You might also recall the datasets past the damaged point individually. When all have been recalled HSEND RECYCLE EXECUTE VOLUME(xxxxxx) FORCE This tape should then free up without a mount. HTH, <snip> I am trying to recycle a damaged ML2 tape. The RECYCLE rolls along however when it hits a particular dsn the recycle terminates. I deleted the migrated dsn (ML2) so as to bypass the problem however it doesn't work. Is there a way of having the RECYCLE bypass this troublesome dsn on the ML2 tape? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
