You'll get the error that DSN17 doesn't match the internal label on the volume. You can either restore the DSN17 field in TMS - or reinitialize the volume.
Jay Campbell IBM OS Support Section -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Eric P. Condon Sent: Thursday, February 12, 2009 3:06 PM To: IBM-MAIN@bama.ua.edu Subject: Re: How to correct tape errors Resurrecting this one - I have changed the DSN17 field to HEXZEROS and run CTSSYNC against the volumes which does indeed clear the error status but TMS appears to continue to reject the volumes when it has the occasion to write to them again. I have another open ticket with CA pending, just wondering if anyone has had a breakthrough on this since it was last discussed in November? ---------------------------------------------------------------------- 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