Richard,

Thank you for the reply.

When each was labeled the activity log shows them as successful after each 
process. My apologizes for leaving that out.

The tapes were used prior to the erase by the same TSM server, library and 
drives without any issues.  I did not get these errors until after I erased 
them on any volume.  I also tried the Wizard to label them and that didn't 
work. It is strange the first time on some of the tapes they mount and data is 
written to them then the next time when TSM goes to access the tape again it 
cannot read the labels.  I really don't understand this. It is like the label 
is not really written to the tapes.

Thank You,
Dan Lane
Systems Administrator
The American Board of Family Medicine, Inc.
(859) 269-5626 - Ext. 293

dlane AT theabfm DOT org - Email

"This email message and any attachments are confidential and may be privileged. 
If you are not the intended recipient, please notify the American Board of 
Family Medicine immediately -- by replying to this message or by sending an 
email to dlane AT theabfm DOT org. If you are not the intended recipient, you 
must immediately destroy all copies of this message and any attachments without 
reading or disclosing their contents. Thank you.
For more information regarding the American Board of Family Medicine, please 
visit us at https://www.theabfm.org/.";



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Richard Sims
Sent: Monday, March 02, 2009 3:33 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] NTUTIL Erase Tape causes an error after checkin and 
labeling the tape.

On Mar 2, 2009, at 11:38 AM, Daniel Lane wrote:

> Hello everyone,
>
> We are using TSM version 5.5.2
>
> We have used the ntutil.exe for long erase to erase some of our
> tapes which was successful.  The issue though is that when the
> tapes are checked back into the library TSM goes to use the tapes
> and cannot read the label.
>
> ANR8311E An I/O error occurred while accessing drive MT0.0.0.3 (\\.
> \Tape1) for READ operation, errno = 1104. (PROCESS: 28)
> ANR8355E I/O error reading label for volume A00017L3 in drive
> MT0.0.0.3 (\\.\Tape1). (PROCESS: 28)
> ANR8778W Scratch volume A00017L3 changed to Private Status to
> prevent re-access. (PROCESS: 28)
> ANR8311E An I/O error occurred while accessing drive MT0.0.0.3 (\\.
> \Tape1) for READ operation, errno = 1104. (PROCESS: 28)
>
> So I have performed "checkout libv LB0.1.0.4 remove=no
> checklabel=no vollist=A00017L3" then "label libv LB0.1.0.4
> search=yes overwrite=yes labelsource=barcode checkin=scratch
> waitt=0 vollist=A00017L3" to each of the tapes.
> TSM then lists the tapes as scratch volumes.  I then see TSM error
> with where the same tape it labeled which is in the library and
> marked as scratch when TSM tries to use it.
>
> ANR8355E I/O error reading label for volume A00017L3 in drive
> MT0.0.0.3 (\\.\Tape1).
> ANR8778W Scratch volume A00017L3 changed to Private Status to
> prevent re-access.
>
> Why are the tapes not being labeled did I do something incorrectly?
>

Your posting doesn't say whether you checked your Activity Log to see
if the Label Libvolume had any problems performing the operation.  Be
sure to check that.

If there was a significant interval between the labeling operating
and TSM's attempted use of the tape, and the library is in any way
shared, it's possible that some action outside of TSM rewrote the
tape and overlaid the labels with data during that interval, just as
ntutil obliterated the labels.

You can verify whether or not there are labels on the tape per the
procedure outlined in IBM Technote 1193760.

    Richard Sims      http://people.bu.edu/rbs/