× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Scott,

Every new tape drive comes up with the next TAPnn number. When it does, simply vary it off, rename it to TAP01 and vary it back on. Of course you'll need to either delete the current TAP01 or rename it prior to renaming the new drive to TAP01.

You can rename TAP01 to anything else and then change the resource name on it to point to whatever comes up when the 3590 is now connected to the loaner card.

Hope that's clear!

- Larry "DrFranken" Bolhuis

On 2/7/2012 3:16 PM, Lindstrom, Scott R. wrote:
Later this month I am going to convert from 3590 to 3580-L33 (LTO3) and am wondering what my best course of action is.

This is a two LPAR system; each LPAR currently has a 3590 with Device Description TAP01 on Resource Name TAP01. I believe the hardware vendor is going to plug the new tape drives into the cards in which the 3590's are currently plugged in.

Should I simply delete Device Description TAP01 [3590] on each LPAR before I bring the systems down so when they come back up they will auto config as TAP01 [3580] again? I don't want them to come up as TAP02 or anything other than TAP01.

Second, on one of the LPARs I will temporarily be loaned an I/O card so we can attach one of the 3590's (then I can DUPTAP some 3590's to LTO3). If I simply hold off on plugging in the 3590 until TAP01 has auto config'ed as TAP01 could I then expect the 3590 to auto config as TAP02?

TIA,
Scott Lindstrom


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.