Here's my 2c worth. The problem is not the library, but the TSM application.
There is a single name space for TSM serial volumes. The short answer is, regardless of how many libraries you have, the tape volume names including primary and secondary pools must be unique across the system. David -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Seay, Paul Sent: Monday, 10 February 2003 12:58 PM To: [EMAIL PROTECTED] Subject: Re: tape cartridges with same bar codes I suspect that you cannot even check both tapes into the library, though I have never done it. This is why. When you check a volume in as scratch it checks the volumes table to make sure the volume is not in the table. This is to protect the volume contents from being destroyed (referential integrity). Before or after this check, do not know which, the checkin is going to fail (private or scratch) because one of the indexes on the libvolumes table is volume_name. A duplicate volume name will occur and the tape checkin will fail. This is the beauty of TSM's referential integrity. It protects us from ourselves. I have not actually done this, but I have a US dollar that says the second checkin/label command will fail. You will be able to insert both tapes into both libraries so long as you are not doing the auto checkin/label function of V5.1. Remember once a tape is in the volumes table it has a device class associated with it. So, you cannot simply move a tape from one library to another. There is no way to update the device class field in the stgpool table. This is a feature I am sure many customers would like to have when they are balancing the usage of multiple libraries. Paul D. Seay, Jr. Technical Specialist Northrop Grumman Information Technology 757-688-8180 -----Original Message----- From: Ki-Hwan Kwon [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 09, 2003 7:55 PM To: [EMAIL PROTECTED] Subject: tape cartridges with same bar codes Hello, To simplify my question, assume that there are two tape cartridges with same bar codes. The tapes are extended high performance tapes. We have two IBM 3494 tape libraries (I call them as 3494A and 3494B each). If I put one tape into 3494A dnd if I put the other tape into 3494B, will this cause a problem to ADSM server due to same bar codes? I have ADSM installed on an RS/6000 unix server which manages the two libraries. I am a newbie in ADSM and someone says this will cause a problem but I don't understand why. Since they are in physically different library, there should be a way to distinguish the two tapes with same bar codes. Any comments will be much appreciated. thanks.