Lambros,
       Thanks for your response! However I have my doubts about your
explanation. I mean 3 gig compression down to 0.05 meg and 0.00 meg is
some compression. Would'nt you say.

>>> Lambros Rizos <rizos AT PFLANZENBAU.UNI-KIEL DOT DE> 05/26/97
12:03am >>>
The MAXSIZE=x in the Storagepool def. is the size of the orig. File.
ADSM reports the size of the compressed file.
I mean the first -2- entries are files that migrate from the Tapepool
to the Tapelarge2.


Tony Pietrusiewicz wrote:
>
> Hi All,
>     Here's the situation.
> I have a DASD primary Backuppool with a maximum file size of 3 Gigs.
> My nextpool isTapepool. Also with a maximum file size of 3 gigs. My
> nextpool for Tapepool is Tapelarge2. Tapelarge2 has an unlimited file
> size.
> I expected Tapelarge2 to only contain files 3 gigs or larger. However I
> noticed several little bitty files when I did a 'query occupancy'. See
> Below.
>
> q occ stg=tapelarge2
>
>  Node Name                Type Filespace   Storage     Number of      Space
>                                Name        Pool Name       Files   Occupied
>                                                                        (MB)
>  ------------------------ ---- ----------- ----------- --------- ----------
>  FDL1                     Bkup FDL1\SYS:   TAPELARGE2          1       0.05M
>  MKTG_SALES1    Bkup MKTG_SALES- TAPELARGE2      1       0.00M
>
>  NTARMS1                  Bkup DATA        TAPELARGE2         10
22,710.03
>  NTARMS2                  Bkup DATA        TAPELARGE2          1   1,687.64
>
> Has anyone else experienced this or know why it happened. I will
> appreciate any remarks.