On 31-Mar-99 Leo Humar wrote:
> Hi Henk,
>
> I have observed reclamation of our copypool volumes and once ADSM has
> reclaimed the data of these volumes they return to the scratch pool.

  No, reclaimed volume still belong to the private pool, because they were
  "checkin" with status=private. For example, vol U00022 (still pending,
  so reclaimed):

dsm> q vol U00022 f=d

                   Volume Name: U00022
             Storage Pool Name: UNITEPOOL
             Device Class Name: 3494-3590
       Estimated Capacity (MB): 0.0
                      Pct Util: 0.0
                 Volume Status: Pending
                        Access: Read/Write
        Pct. Reclaimable Space: 0.0
               Scratch Volume?: No
               In Error State?: No
      Number of Writable Sides: 1
       Number of Times Mounted: 29
             Write Pass Number: 1
     Approx. Date Last Written: 03/10/99   14:22:21
        Approx. Date Last Read: 03/29/99   08:22:45
           Date Became Pending: 03/29/99   10:35:49
        Number of Write Errors: 0
         Number of Read Errors: 0
               Volume Location:
Last Update by (administrator): ADMIN
         Last Update Date/Time: 03/02/99   15:05:53


adsm> q libvol * U00022

Library Name    Volume Name    Status               Last Use     Home Element
------------    -----------    -----------------    ---------    ------------
3494LIB         U00022         Private              Data
3494LIB         U00022         Private              Data


The point is, volume U00020 does not exist anymore in the storage pool as
I mentioned before:

adsm> q vol U00020
ANR2034E QUERY VOLUME: No match found using this criteria.
ANS8001I Return code 11.

> Can you check volume U00020 with q volume f=d and compare it with this
> example?

  No, I can't.

> I don't think that there is anything to worry about.

  I think, no I'am sure, there is much to worry about.

  Cheers,
  Henk ten Have.