Eric,
I'd try to rename the existing storagepool to a temporary name (rename
stgpool).
Then you can create a new pool with the old name, so your documentation
remains up to date.
With two tapepools you'll have the advantage that you can adjust space
reclamation and migration settings (next stgpool) without affecting the
new pools settings.

Good luck,
best regards,
Michael
--
Michael Bartl                               mailto:michael.bartl AT cw DOT com
Michael Bartl                               mailto:michael.bartl AT cw DOT com
Office of Technology, IT Germany/Austria    Tel: +49-89-92699-806
Cable & Wireless Deutschland GmbH.          Fax: +49-89-92699-302
Landsberger Str. 155, D-80687 Muenchen      http://www.cw.com/de


"Loon, E.J. van - SPLXM" wrote:
>
> Hi *SM-ers!
> I will receive a new library tomorrow. We will switch from a 3494 to a
> Ultrium 3584.
> I will have to migrate all my data to the new library, but I don't want to
> create new storagepools (standard naming convention, listed in various
> reference support manuals you know...).
> My current tapepool is using deviceclass 3590, what happens when I change
> the device class for the tapepool to the newly created deviceclass 3580? Can
> I still access the 'old' data on 3590 tapes? If so, I can use the next
> storage pool parameter to migrate all 3590 data to the new 3580 tapes, while
> all diskpool migrations go to the new 3580 devices.
> Thanks in advance for any reply!
> Kindest regards,
> Eric van Loon
> KLM Royal Dutch Airlines
>
> **********************************************************************
> This e-mail and any attachment may contain confidential and privileged 
> material intended for the addressee only. If you are not the addressee, you 
> are notified that no part of the e-mail or any attachment may be disclosed, 
> copied or distributed, and that any other action related to this e-mail or 
> attachment is strictly prohibited, and may be unlawful. If you have received 
> this e-mail by error, please notify the sender immediately by return e-mail, 
> and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its 
> subsidiaries and/or its employees shall not be liable for the incorrect or 
> incomplete transmission of this e-mail or any attachments, nor responsible 
> for any delay in receipt.
> **********************************************************************