Amazingly enough, if you do not rename the library, it may not have an
effect at all.  I have LTO2's and LTO3's in the same library, the LTO2's
were mostly all labeled before we turned on the full label viewing for
the LTO3's.  The interesting thing is that to this day (almost 2 years
after turning it on) TSM still labels LTO2s with the short name (without
the L2) and labels the LTO3's with the long name (with the L3).

If you have new tapes you could change the label to see the full 8
characters, then try to label some of the older tapes to see what
happens.  We use an IBM 3584 (TS3500) Library, so YMMV.

See Ya'
Howard Coles Jr.
John 3:16!


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Shawn Drew
Sent: Friday, March 19, 2010 2:19 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Rename volumes or other workaround

A few years ago, when TSM was first implemented here, the ADIC i2000 was
set so that the L3 suffix was not passed to TSM.
For many reasons I would like to change this to include the suffix.

The main problem I see is that when we need to read from any of the old
tapes, TSM will look for the old tape label.

The only way I could imagine doing this is by partitioning the library
and
hoping that it will let me have a different barcode rule for each
partition.  Then, migrate the data from one partition (without the
suffix)
to the new partition (with the suffix)
After that, I would have to redefine all of our backupsets and migrate
all
of our (thousands of tapes) ndmp data.

In other words, I am NOT going to do that.   Is there any, possibly
undocumented,  way to rename the volumes in TSM 5.5?


Regards,
Shawn
________________________________________________
Shawn Drew


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in
error,
please delete it and immediately notify the sender. Any use not in
accord
with its purpose, any dissemination or disclosure, either whole or
partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall
(will)
not therefore be liable for the message if modified. Please note that
certain
functions and services for BNP Paribas may be performed by BNP Paribas
RCC, Inc.