I see no reason why not. However, make sure the printed labels and vol labels agree.
I suspect they will have to have separate category codes and be separate logical libraries. That's how I would do it to keep everything straight and minimize the possibility of errors. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Monday, October 15, 2012 2:50 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] re-label 3592-3C as 3592-2C ? Sure. We did this a lot when moving between formats like you (we are now all E06). Check out the LABEL LIBVOLUME command. I don't know the 3584 (we have a 3494) but you might be able to set the library attributes to auto-relabel. On Mon, Oct 15, 2012 at 2:13 PM, Arbogast, Warren K <warbo...@indiana.edu>wrote: > Both of our TSM/EE servers are at version 6.3.2 running on RHEL5. > > Each server has a 3584 ATL attached to it with both 3592-E06 and 3592-E05 > tape drives installed. The 3592-E05 drives were not removed when the > 3592-E06 drives were added. Now we have an urgent need for more tape > drives, and we are to use the 3592-E05 drives to fulfill that need. All > 3592-JB cartridges in the 3584 have already been written to by a 3592-E06 > drive, and there is no budget for new cartridges. There should be enough > scratch tapes for the new data, they're just the wrong format. > > A 3592-E05 drive cannot read or write a cartridge that has been written by > a 3592-E06 drive. A process is needed to re-label or re-format a set of > cartridges for the exclusive use of the 3592-E05 drives. Can this be done > with TSM? Or, can it be done with IBM Tape Diagnostic Tool ? > > Thank you, > Keith Arbogast > -- *Zoltan Forray* TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
