That is what I have done. I don't know of a better or different way.

One thought that IBM seems to be encouraging is to use FILE devclass for
disk storage pools vs the traditional pool & volumes.  This way you don't
have the additional process of formatting storage pool volumes.

Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT 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


From:
"Lee, Gary D." <GLEE AT BSU DOT EDU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
07/09/2010 09:52 AM
Subject:
[ADSM-L] Shrinking a disk pool
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Tsm server 5.5.4
Suse sles9 under VM 5.3

I have a TSM server running as back end storage for IBM content
manager/Ondemand and content manager itself.

The OnDemand piece uses archive storage and the content manager uses
backups.

I would like to shrink the archive pool and re-allocate that storage to
the backup pool.

I have considered marking the re-allocatable olumes read only, then doing
a move data volume_name within the pool, then deleting the empty volume
and redefining to the backup pool.
Is there an easier  way that I haven't seen?

Thank you for your time and consideration.