We bought it back from offsite vault and did not want it to be revaulted.
Doesn't seem to matter what the ACCESS is set to.  Tried it all different
ways.  Either way....a delete should be a delete.



From:
Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
05/21/2010 11:15 AM
Subject:
Re: [ADSM-L] Deleting ghost/empty volume on V6.1 server
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



Access is read-only?

Thank you,
~Rick


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Friday, May 21, 2010 11:04 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Deleting ghost/empty volume on V6.1 server

Sorry....my bad.......................It is a copypool volume.


                   Volume Name: 086176
             Storage Pool Name: COPYPOOL-TS1130
             Device Class Name: 3592-E06
            Estimated Capacity: 1.5 T
       Scaled Capacity Applied: 100
                      Pct Util: 0.6
                 Volume Status: Filling
                        Access: Read-Only
        Pct. Reclaimable Space: 39.3
               Scratch Volume?: Yes
               In Error State?: No
      Number of Writable Sides: 1
       Number of Times Mounted: 1
             Write Pass Number: 1
     Approx. Date Last Written: 02/22/2010 23:51:41
        Approx. Date Last Read: 02/22/2010 22:22:06
           Date Became Pending:
        Number of Write Errors: 0
         Number of Read Errors: 0
               Volume Location:
Volume is MVS Lanfree Capable : No
Last Update by (administrator): TSMMANAGER
         Last Update Date/Time: 05/21/2010 08:27:59
          Begin Reclaim Period:
            End Reclaim Period:
  Drive Encryption Key Manager: None



From:
Richard Sims <rbs AT BU DOT EDU>
To:
ADSM-L AT VM.MARIST DOT EDU
Date:
05/21/2010 10:35 AM
Subject:
Re: [ADSM-L] Deleting ghost/empty volume on V6.1 server
Sent by:
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



We know nothing about your volume; but if it is a primary pool tape, and
there is a current copy storage pool, you could try a Restore Volume and
see what happens (no guarantees here, either).  My sense is that you'll
have to contact TSM Support for assistance in resolving this.

   Richard Sims