At 11:29 AM -0400 10/22/02, David Longo said:

With checklabel=barcode, what happens is that TSM reads the internal
memory of the library as to what the library's inventory says is
where.

So checklabel=barcode doesn't really mean read the barcodes?  It just
means check the library's internal memory?  I guess that's still
useful in some circumstances, if there'e a possibility that TSM and
the library have gotten out of sync.
But it would be nice if things mean what they say.  Suppose I really
want it to read the barcodes?  Suppose I think the library's internal
memory has gotten confused somehow, and I  want to do a physical
audit of barcode locations to compare with the internal memory?  Is
this possible? Or is it a function of the library (which I guess
might  make more sense).

So generally that won't take long.  And a drive needs to be available
for
the case where library had a problem reading a barcode label, that
tape
can be mounted in a tape drive to verify - even if using checkl=b.

But how can it have a problem reading the barcode label if check-=b
doesn't even try to read the labels?



--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506
<mailto:msimpson AT uky DOT edu>
mainframe --   An obsolete device still used by thousands of obsolete
companies serving billions of obsolete customers and making huge obsolete
profits for their obsolete shareholders.  And this year's run twice as fast
as last year's.