Re: Audit Library question.

[David Longo]

My 3584-L32 with FC-AL drives takes less than 20 seconds on
AIX with TSM 4.2.2.10.

David Longo

>>> [EMAIL PROTECTED] 10/18/02 10:43PM >>>
I have had it hang up when I had a drive failure with a tape stuck in
the
drive. But it usually only takes 5 minutes for my 3584 with fibre
channel
LTO drives. I am running TSM 5.1.1 on win2k.
--
Thanks,
Matt

-Original Message-
From: Todd Lundstedt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Sent: Fri Oct 18 11:41:46 2002
Subject: Audit Library question.

How long should the command
"Audit Library LibName CheckLabel=BARCODE"
take to process.  I have less than 200 tapes in the library.  I have
done
this before and it took less than 5 mins.  This one has been running
for
over 40 minutes now.  The processor is 99-100% idle.  No tapes in use.
All
reclamation set to 100 to prevent tapes from being used.

TSM 4.2.1.7
AIX 4.3.3
IBM LTO Ultrium drives in 3584 library.

Thanks in advance.


"MMS " made the following
 annotations on 10/19/2002 07:34:09 PM
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: Audit Library question.

[Matt Simpson]

At 10:41 AM -0500 10/18/02, Todd Lundstedt said:

How long should the command
"Audit Library LibName CheckLabel=BARCODE"
take to process.  I have less than 200 tapes in the library.  I have done
this before and it took less than 5 mins.  This one has been running for
over 40 minutes now.


Our situation is just the opposite.  We have a 3584 library connected
to TSM 4.2.2.0 on Solaris.
Audit Library LibName CheckLabel=BARCODE
completes in a few seconds, with no movement of the library robotics.
It doesn't appear to be checking any barcodes at all. I haven't tried
it with CHecklabel=Yes yet.
--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506

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.

Re: Audit Library question.

[David Longo]

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 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.



David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/02 08:27AM >>>
At 10:41 AM -0500 10/18/02, Todd Lundstedt said:
>How long should the command
>"Audit Library LibName CheckLabel=BARCODE"
>take to process.  I have less than 200 tapes in the library.  I have
done
>this before and it took less than 5 mins.  This one has been running
for
>over 40 minutes now.

Our situation is just the opposite.  We have a 3584 library connected
to TSM 4.2.2.0 on Solaris.
Audit Library LibName CheckLabel=BARCODE
completes in a few seconds, with no movement of the library robotics.
It doesn't appear to be checking any barcodes at all. I haven't tried
it with CHecklabel=Yes yet.
--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506

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.


"MMS " made the following
 annotations on 10/22/2002 11:30:57 AM
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: Audit Library question.

[Matt Simpson]

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

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.

Re: Audit Library question.

[David Longo]

I imagine the checkl=barocde was introduced to shorten audit, without
it you would have to mount every tape in library - which would take
some considerable time with some libraries!  What you are doing is
checkinbg the barcode label in library memory as opposed to checking
the
magnetic tape label header.

The ideal short way is to have the library do it's inventory, which
reads
barcodes and is quick, then do audit with checkl=barcode.  Whole
process shouldn't take more than a few minutes - there may be some
library units that take longer.  This complete process should take
care
of anything that has gotten out of sync.  I have had a few cases where
there was still something out of sync and had to do detailed
examination
to correct.

It can have  a problem reading the barcode if the laser scanner
couldn't
read the label.  That can happen some times - especially if you don't
use
original manufacturers labels.  If you have AIX server and use
tapeutil
with inventory action, it will show the slot status for tapes like
these
in "abnormal" status.  When the audit with checkl=barcode runs it
finds
this and no barcode label for that slot and mounts the tape in that
slot
to read the magnetic label and update TSM's inventory.

A brief overview as I have seen it in action many times.



David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/02 01:44PM >>>
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

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.


"MMS " made the following
 annotations on 10/22/2002 02:04:16 PM
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==

Re: Audit Library question.

[KEN HORACEK]

Not true...
With checklabel=barcode, all of the barcodes are read.  This is then checked with the 
internal memory of the library as to what the library's inventory says is where.  The 
tape is mounted, only if the barcode is mis-read.

Ken
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/2002 10:44:50 AM >>>
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

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.

-
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
-
<<<>>>

Re: Audit Library question.

[Todd Lundstedt]

The reason I started the audit was because TSM was not reporting the tape
in the library, yet the library knew the tape was inserted.  I could see
the tape in the library (with my own eyes).  Using the manual operations |
move tape functions from the LCD display on the library, the library was
able to move the tape out and back into the library.  But Query LIBVolume
did not show the tape in the library.
I thought Audit Library with checklabel=barcode should fix it, but after 2
hours, the process hadn't ended.  So I cancelled it.
What I ended up doing was manually removed the tape (via the move tape
functions from the LCD panel of the library), and then turned around and
did a Checkin process for the tapes in the Bulk I/O slots.  After that, the
query libvolume command reported the tape in the library.
This tells me that there is/was no problem with the barcode, or the reader,
and possibly even the library memory (since the library knew it had the
tape all along).  Something funky going on with the Audit Library process,
for sure.



|+-->
||  David Longo |
|||
||  Sent by: "ADSM: Dist|
||  Stor Manager"   |
||  <[EMAIL PROTECTED]|
||  U>  |
||  |
||  |
||  10/22/2002 01:02 PM |
||  Please respond to   |
||  "ADSM: Dist Stor|
||  Manager"|
||  |
|+-->
  
>---|
  |
   |
  |  To: [EMAIL PROTECTED]  
   |
  |  cc:   
   |
  |  Fax to:   
       |
  |  Subject: Re: Audit Library question.  
   |
  
>---|




I imagine the checkl=barocde was introduced to shorten audit, without
it you would have to mount every tape in library - which would take
some considerable time with some libraries!  What you are doing is
checkinbg the barcode label in library memory as opposed to checking
the
magnetic tape label header.

The ideal short way is to have the library do it's inventory, which
reads
barcodes and is quick, then do audit with checkl=barcode.  Whole
process shouldn't take more than a few minutes - there may be some
library units that take longer.  This complete process should take
care
of anything that has gotten out of sync.  I have had a few cases where
there was still something out of sync and had to do detailed
examination
to correct.

It can have  a problem reading the barcode if the laser scanner
couldn't
read the label.  That can happen some times - especially if you don't
use
original manufacturers labels.  If you have AIX server and use
tapeutil
with inventory action, it will show the slot status for tapes like
these
in "abnormal" status.  When the audit with checkl=barcode runs it
finds
this and no barcode label for that slot and mounts the tape in that
slot
to read the magnetic label and update TSM's inventory.

A brief overview as I have seen it in action many times.



David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/02 01:44PM >>>
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 g

Re: Audit Library question.

[Todd Lundstedt]

Not true on my library, Ken...
I have run several audits using checklabel=barcode before with success.
The arm has never moved in the library with an audit using checkl=b.



|+>
||  KEN HORACEK   |
||  |
||  Sent by:  |
||  "ADSM: Dist   |
||  Stor Manager" |
||  <[EMAIL PROTECTED]|
||  IST.EDU>  |
|||
|||
||  10/22/2002|
||  01:03 PM  |
||  Please respond|
||  to "ADSM: Dist|
||  Stor Manager" |
|||
|+>
  
>---|
  |
   |
  |  To: [EMAIL PROTECTED]  
   |
  |  cc:   
   |
  |  Fax to:   
   |
  |  Subject: Re: Audit Library question.  
   |
  
>---|




Not true...
With checklabel=barcode, all of the barcodes are read.  This is then
checked with the internal memory of the library as to what the library's
inventory says is where.  The tape is mounted, only if the barcode is
mis-read.

Ken
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/2002 10:44:50 AM >>>
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@;uky.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.

-
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
-
<<<>>>

Re: Audit Library question.

[Cook, Dwight E]

All depends on your type of library !

IBM 3494-L12

To get the atl to actually scan the barcodes of the tapes you must go to the
operator console and do a
command, inventory, inventory update full
or something close to that (changes across levels of the library manager
code)
then inside tsm an audit library checklabel=barcode only checks against the
library manager's data base.

Dwight


-Original Message-
From: KEN HORACEK [mailto:KHORACEK@;INCSYSTEM.COM]
Sent: Tuesday, October 22, 2002 1:03 PM
To: [EMAIL PROTECTED]
Subject: Re: Audit Library question.


Not true...
With checklabel=barcode, all of the barcodes are read.  This is then checked
with the internal memory of the library as to what the library's inventory
says is where.  The tape is mounted, only if the barcode is mis-read.

Ken
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/2002 10:44:50 AM >>>
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@;uky.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.

-
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
-
<<<>>>

Re: Audit Library question.

[Murray, Jim]

Not so here with an ATL 7100 checklabel=barcode and it Always moves up and
down the rows, can only assume it is reading as it goes.

Jim Murray
Senior Systems Engineer
Liberty Bank
860.638.2919
[EMAIL PROTECTED]
"I hear and I forget.
I see and I remember.
I do and I understand."
 -Confucius



-Original Message-
From: Todd Lundstedt [mailto:Todd_Lundstedt@;VIA-CHRISTI.ORG]
Sent: Tuesday, October 22, 2002 14:28
To: [EMAIL PROTECTED]
Subject: Re: Audit Library question.


Not true on my library, Ken...
I have run several audits using checklabel=barcode before with success.
The arm has never moved in the library with an audit using checkl=b.



|+>
||  KEN HORACEK   |
||  |
||  Sent by:  |
||  "ADSM: Dist   |
||  Stor Manager" |
||  <[EMAIL PROTECTED]|
||  IST.EDU>  |
|||
|||
||  10/22/2002|
||  01:03 PM  |
||  Please respond|
||  to "ADSM: Dist|
||  Stor Manager" |
|||
|+>

>---
|
  |
|
  |  To: [EMAIL PROTECTED]
|
  |  cc:
|
  |      Fax to:
|
  |  Subject: Re: Audit Library question.
|

>---
|




Not true...
With checklabel=barcode, all of the barcodes are read.  This is then
checked with the internal memory of the library as to what the library's
inventory says is where.  The tape is mounted, only if the barcode is
mis-read.

Ken
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/2002 10:44:50 AM >>>
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@;uky.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.

-
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
-
<<<>>>



The information transmitted is intended only for the person
or entity to which it is addressed and may contain confidential
and/or privileged material. If you are not the intended
recipient of this message you are hereby notified that any use,
review, retransmission, dissemination, distribution, reproduction
or any action taken in reliance upon this message is prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.  Any views expressed
in this message are those of the individual sender and may
not necessarily reflect the views of the company.

Re: Audit Library question.

[Matt Simpson]

At 11:03 AM -0700 10/22/02, KEN HORACEK said:

With checklabel=barcode, all of the barcodes are read.  This is then
checked with the internal memory of the library as to what the
library's inventory says is where.


That's not what I'm seeing, and that's not what I think I'm reading
from others here.
When I execute the audit checklabel=barcode for our 3584 library, it
completes almost instantaneously with no movement of the library
robotics.  I don't see how it could possibly be reading the barcode
labels.  I suspect it's doing what I think others have suggested:
"remembering" the barcode labels that it has read previously.

At 2:02 PM -0400 10/22/02, David Longo wrote:

I imagine the checkl=barocde was introduced to shorten audit, without
it you would have to mount every tape in library - which would take
some considerable time with some libraries!


I understand that reading the barcode is a good alternative to
mounting the tape and reading the internal label.  But what I'm
saying is that it doesn't appear to be reading the barcodes when the
audit is executed.


 What you are doing is
checkinbg the barcode label in library memory as opposed to checking
the
magnetic tape label header.


That's what I thought .. checking the barcode label in library
memory.  But in my interpretation, checklabel=barcode should mean
read the barcode now, not tell me what it thinks it is based on its
memory of the last time  it read it.



The ideal short way is to have the library do it's inventory, which
reads
barcodes and is quick, then do audit with checkl=barcode.


OK .. thatmakes sense.  The library inventory physically reads the
barcode labels and updates the internal memory if necessary, and then
the TSM audit checklabel=barcode causes the library's memory to be
synced with TSM.  In my opinion, the ideal short way  would be to
have the TSM audit checklabel=barcode command really tell the library
to read the barcodes, eliminating the need to do the library
inventory in a previous step.   When I say checklabel=barcode, I mean
checklabel=barcode, I don't mean check your internal memory. But I
don't know if that's a limitation in the library or TSM.

--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506

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.

Re: Audit Library question.

[Kauffman, Tom]

This seems to be library dependent. We've had both an STK 9710 and an IBM
3584. Both of these libraries, as a function of library startup (or after
the door had been opened/closed) would scan all slots and build an in-memory
list of volumes and slots in the controller.

Any TSM library audit with checklabel=barcode just gets back the volser and
slot from the library; if the library has an internal memory, it should come
from there. Without an internal data store of some kind, it will need to
scan the tapes.


Tom Kauffman
NIBCO, Inc

> -Original Message-
> From: Murray, Jim [mailto:JMurray@;LIBERTY-BANK.COM]
> Sent: Tuesday, October 22, 2002 1:46 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Audit Library question.
>
>
> Not so here with an ATL 7100 checklabel=barcode and it Always
> moves up and
> down the rows, can only assume it is reading as it goes.
>
> Jim Murray
> Senior Systems Engineer
> Liberty Bank
> 860.638.2919
> [EMAIL PROTECTED]
> "I hear and I forget.
> I see and I remember.
> I do and I understand."
>  -Confucius
>
>
>
> -Original Message-
> From: Todd Lundstedt [mailto:Todd_Lundstedt@;VIA-CHRISTI.ORG]
> Sent: Tuesday, October 22, 2002 14:28
> To: [EMAIL PROTECTED]
> Subject: Re: Audit Library question.
>
>
> Not true on my library, Ken...
> I have run several audits using checklabel=barcode before
> with success.
> The arm has never moved in the library with an audit using checkl=b.
>
>
>
> |+>
> ||  KEN HORACEK   |
> ||   ||  YSTEM.COM>|
> ||  Sent by:  |
> ||  "ADSM: Dist   |
> ||  Stor Manager" |
> ||  <[EMAIL PROTECTED]|
> ||  IST.EDU>  |
> |||
> |||
> ||  10/22/2002|
> ||  01:03 PM  |
> ||  Please respond|
> ||  to "ADSM: Dist|
> ||  Stor Manager" |
> |||
> |+>
>
> >---------
> --
> |
>   |
> |
>   |  To: [EMAIL PROTECTED]
> |
>   |  cc:
> |
>   |  Fax to:
> |
>   |  Subject: Re: Audit Library question.
> |
>
> >-
> --
> |
>
>
>
>
> Not true...
> With checklabel=barcode, all of the barcodes are read.  This is then
> checked with the internal memory of the library as to what
> the library's
> inventory says is where.  The tape is mounted, only if the barcode is
> mis-read.
>
> Ken
> [EMAIL PROTECTED]
>
>
> >>> [EMAIL PROTECTED] 10/22/2002 10:44:50 AM >>>
> 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@;uky.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.
>
> -

Re: Audit Library question.

[KEN HORACEK]

We too have a 3584.  When an AUDIT LIBRARY checklabel=barcode (run daily) occurs, the 
arm moves over the entire library of tapes, reading the barcodes.  I have witnessed 
this.  If there is something that was done at installation time, of our LTO, to effect 
this, I couldn't say.  Maybe someone out there, intimate with the hardware, can let us 
all know.


Ken
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/2002 11:53:54 AM >>>
At 11:03 AM -0700 10/22/02, KEN HORACEK said:
>With checklabel=barcode, all of the barcodes are read.  This is then
>checked with the internal memory of the library as to what the
>library's inventory says is where.

That's not what I'm seeing, and that's not what I think I'm reading
from others here.
When I execute the audit checklabel=barcode for our 3584 library, it
completes almost instantaneously with no movement of the library
robotics.  I don't see how it could possibly be reading the barcode
labels.  I suspect it's doing what I think others have suggested:
"remembering" the barcode labels that it has read previously.

At 2:02 PM -0400 10/22/02, David Longo wrote:
>I imagine the checkl=barocde was introduced to shorten audit, without
>it you would have to mount every tape in library - which would take
>some considerable time with some libraries!

I understand that reading the barcode is a good alternative to
mounting the tape and reading the internal label.  But what I'm
saying is that it doesn't appear to be reading the barcodes when the
audit is executed.

>  What you are doing is
>checkinbg the barcode label in library memory as opposed to checking
>the
>magnetic tape label header.

That's what I thought .. checking the barcode label in library
memory.  But in my interpretation, checklabel=barcode should mean
read the barcode now, not tell me what it thinks it is based on its
memory of the last time  it read it.

>
>The ideal short way is to have the library do it's inventory, which
>reads
>barcodes and is quick, then do audit with checkl=barcode.

OK .. thatmakes sense.  The library inventory physically reads the
barcode labels and updates the internal memory if necessary, and then
the TSM audit checklabel=barcode causes the library's memory to be
synced with TSM.  In my opinion, the ideal short way  would be to
have the TSM audit checklabel=barcode command really tell the library
to read the barcodes, eliminating the need to do the library
inventory in a previous step.   When I say checklabel=barcode, I mean
checklabel=barcode, I don't mean check your internal memory. But I
don't know if that's a limitation in the library or TSM.

--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506

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.

-
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
-
<<<>>>

Re: Audit Library question.

[David Longo]

Following the discussion here (and in past months), part of the
problem is the way libraries respond.  I believe (Tivoli maybe coluld
chime in and give the fine points on this) that when audit library
checkl=barcode is issued that a certain SCSI command is sent to
library.
With the varied libraries out there supported, from simple to complex,
the library interprets the command slightly differently in what it is
requested to do.  So as they say on TV "Your results may not be the
same" - or is that what your stock broker says?

On the things getting out of sync question.  I just looked at the help
audit library command on a TSM 4.2.2.10 server.  Notice the wording
carefully:

"TSM deletes missing volumes and updates moved volume locations. TSM
does not automatically add new volumes; you must check in new volumes
with the CHECKIN LIBVOLUME command."

I think the implication is that it does nothing else.  That is if you
manually
put a tape in the library without the checkin command and then run
inventory/audit, TSM wil not pick it up.

Also for instance in cases I have personally seen, if you do a
checkout
and bulk I/O is full, the the prompt to operators is to remove tape
xxx
from slot yyy.  If the operator isn't paying attention and replies to
this,
then that tape is removed from TSM inventory but is STILL in the
library.
An audit and inventory will not put it back up into TSM's inventory.
There
are a few other slight variations  on this that I have seen, but you
get the idea.  I believe these circumstnace would be the same for
all automated libraries but am not completely sure.

How do you find these tapes then?  Send me $5.95 plus shipping
and handling and I'll send you instructions on how!  But seriously
folks, that's what they pay us the BIG bucks for.  In a sentence
of two: run a q libvol from TSM and in very close time sequence
run an inventory for your library with say tapeutil.  (Tapeutil
will show ALL tapes, no matter how they got in library).  Then do
a comparison.  Some libraries you may have to open and do a slot
by slot comparison.

As an alternative to q libvol which puts tapes in volser order use this
select
which puts them in element order:

select volume_name,home_element from libvolumes order by home_element


David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH  321.434.5536
Pager  321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/02 02:53PM >>>
At 11:03 AM -0700 10/22/02, KEN HORACEK said:
>With checklabel=barcode, all of the barcodes are read.  This is then
>checked with the internal memory of the library as to what the
>library's inventory says is where.

That's not what I'm seeing, and that's not what I think I'm reading
from others here.
When I execute the audit checklabel=barcode for our 3584 library, it
completes almost instantaneously with no movement of the library
robotics.  I don't see how it could possibly be reading the barcode
labels.  I suspect it's doing what I think others have suggested:
"remembering" the barcode labels that it has read previously.

At 2:02 PM -0400 10/22/02, David Longo wrote:
>I imagine the checkl=barocde was introduced to shorten audit, without
>it you would have to mount every tape in library - which would take
>some considerable time with some libraries!

I understand that reading the barcode is a good alternative to
mounting the tape and reading the internal label.  But what I'm
saying is that it doesn't appear to be reading the barcodes when the
audit is executed.

>  What you are doing is
>checkinbg the barcode label in library memory as opposed to checking
>the
>magnetic tape label header.

That's what I thought .. checking the barcode label in library
memory.  But in my interpretation, checklabel=barcode should mean
read the barcode now, not tell me what it thinks it is based on its
memory of the last time  it read it.

>
>The ideal short way is to have the library do it's inventory, which
>reads
>barcodes and is quick, then do audit with checkl=barcode.

OK .. thatmakes sense.  The library inventory physically reads the
barcode labels and updates the internal memory if necessary, and then
the TSM audit checklabel=barcode causes the library's memory to be
synced with TSM.  In my opinion, the ideal short way  would be to
have the TSM audit checklabel=barcode command really tell the library
to read the barcodes, eliminating the need to do the library
inventory in a previous step.   When I say checklabel=barcode, I mean
checklabel=barcode, I don't mean check your internal memory. But I
don't know if that's a limitation in the library or TSM.

--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506

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

Re: Audit Library question.

[KEN HORACEK]

Todd,
Apparently, not all LTO(s) are created equally.  We have a 3584.



Ken
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/2002 11:28:28 AM >>>
Not true on my library, Ken...
I have run several audits using checklabel=barcode before with success.
The arm has never moved in the library with an audit using checkl=b.



|+>
||  KEN HORACEK   |
||  |
||  Sent by:  |
||  "ADSM: Dist   |
||  Stor Manager" |
||  <[EMAIL PROTECTED]|
||  IST.EDU>  |
|||
|||
||  10/22/2002|
||  01:03 PM  |
||  Please respond|
||  to "ADSM: Dist|
||  Stor Manager" |
|||
|+>
  
>---|
  |
   |
  |  To: [EMAIL PROTECTED]  
   |
  |  cc:   
   |
  |  Fax to:   
           |
  |  Subject: Re: Audit Library question.  
   |
  
>---|




Not true...
With checklabel=barcode, all of the barcodes are read.  This is then
checked with the internal memory of the library as to what the library's
inventory says is where.  The tape is mounted, only if the barcode is
mis-read.

Ken
[EMAIL PROTECTED]


>>> [EMAIL PROTECTED] 10/22/2002 10:44:50 AM >>>
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@;uky.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.

-
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
-
<<<>>>

Re: Audit Library question.

[Tab Trepagnier]

Matt,

What I see on my system depends on the library.  I currently have a 3583,
two 3575s (and L12 and an L18), and an HP 4/40 DLT.  In the past I've used
a smaller 3575 (L06) and a 3570.  All have/had barcode readers.

The two largest 3575s perform barcode audits without moving anything. They
seem to simply read the library's internal inventory back to TSM.  If the
library's inventory is suspect, there is a front panel function to "init
element status" that causes the robot to scan all the bar codes and update
the library's inventory.

The 3570, 3575-L06, and HP 4/40 all send/sent the robot scanning the tapes
in their slots and drives.  That updated info was then reported to TSM.

I don't know what the 3583 does because it doesn't have any windows to
permit viewing the internals while in operation.

Tab Trepagnier
TSM Administrator
Laitram Corporation







Matt Simpson <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
10/22/2002 01:53 PM
Please respond to "ADSM: Dist Stor Manager"


    To: [EMAIL PROTECTED]
cc:
Subject:Re: Audit Library question.


At 11:03 AM -0700 10/22/02, KEN HORACEK said:
>With checklabel=barcode, all of the barcodes are read.  This is then
>checked with the internal memory of the library as to what the
>library's inventory says is where.

That's not what I'm seeing, and that's not what I think I'm reading
from others here.
When I execute the audit checklabel=barcode for our 3584 library, it
completes almost instantaneously with no movement of the library
robotics.  I don't see how it could possibly be reading the barcode
labels.  I suspect it's doing what I think others have suggested:
"remembering" the barcode labels that it has read previously.

At 2:02 PM -0400 10/22/02, David Longo wrote:
>I imagine the checkl=barocde was introduced to shorten audit, without
>it you would have to mount every tape in library - which would take
>some considerable time with some libraries!

I understand that reading the barcode is a good alternative to
mounting the tape and reading the internal label.  But what I'm
saying is that it doesn't appear to be reading the barcodes when the
audit is executed.

>  What you are doing is
>checkinbg the barcode label in library memory as opposed to checking
>the
>magnetic tape label header.

That's what I thought .. checking the barcode label in library
memory.  But in my interpretation, checklabel=barcode should mean
read the barcode now, not tell me what it thinks it is based on its
memory of the last time  it read it.

>
>The ideal short way is to have the library do it's inventory, which
>reads
>barcodes and is quick, then do audit with checkl=barcode.

OK .. thatmakes sense.  The library inventory physically reads the
barcode labels and updates the internal memory if necessary, and then
the TSM audit checklabel=barcode causes the library's memory to be
synced with TSM.  In my opinion, the ideal short way  would be to
have the TSM audit checklabel=barcode command really tell the library
to read the barcodes, eliminating the need to do the library
inventory in a previous step.   When I say checklabel=barcode, I mean
checklabel=barcode, I don't mean check your internal memory. But I
don't know if that's a limitation in the library or TSM.

--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506
<mailto:msimpson@;uky.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.