Clint,

Hmmmm, this seems familiar to a problem that we had with our STK9730.  I
had forgotten to use the LABEL LIBV command and give the tapes an internal
label before checking in the tapes.  Since you used the CHECKLABEL=BARCODE
parameter when checking in the tapes, the library didn't look for an
internal label on the tapes and so there didn't seem to be a problem.
What I'm thinking that happened (as was in our case) is that when you
tried to do a DB BACKUP, it didn't find an internal label on the first
scratch tape it selected, and so it spat out the I/O error.  What I did to
fix the problem was to check out all the tapes (with CHECKLABEL=NO so it
doesn't look for tape's internal label) and then do the LABEL LIBV
command. You can include the parameter CHECKIN=SCRATCH to check them in at
the same time they are labeled.  Also, you can do HELP LABEL LIBV for more
info.

Hope this applies to your situation,

adam

Clint Placette wrote:

> Hello,
>
> I just brought a secondy Library on line.  A stk 9740 with 9840
> drives.  I did an audit of the lib and all 170 volumes came up.  I
> then issued a CHEKIN LIBV TEKWOLF VOLRANGE=000000,000169 STAT=SCRATCH
> CHECKLABEL=BARCODE SEARCH=YES.  This work made all volume into
> scratches.
>
> Here is where it gets hairy.  I decided to due a database back to the
> new LIB.  What I got was the LIB went to each volume marking each
> volume to private (170).  It was trying to due a db backup but it kept
> getting this error ANR8355E I/O error reading label fo volume ### in
> drive  ##.
>
> Well I decide to call IBM they wanted me to audit the LIB again.  This
> proved fruital because after the audit it blew away all the volumes.
> I bet you can't guess what I am doing right now.  Yes that's right I
> am auditing the LIB again.
>
> Can anybody help me on this.
>
> AIX 4.2.1
> ADSM 3.2.1.40

--
__________________
__________________
Adam Slesinger
Corporate Information Systems
Brown & Sharpe, RI
Phone: (401) 886-2236
Pager: (800) 913-5395
Email: aslesinger AT us.bnsmc DOT com