Just my $.02

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: Re: Little Bitty Files in My 3 Gig Pool -Reply
Author:  INTERNET.OWNERAD at SNADGATE
Date:    5/29/97 11:19 AM


Sorry Tony,
a) I mean Diskpool--> Tapepool --> Tapelarge2.
b) I have queried my environment.The  results:

q cont vol007 f=d

             Node Name: NODE29
                  Type: Bkup
        Filespace Name: WINDOWS95
Client's Name for File: \USER\DATEN\WORDD\DISS TODAY\ABBILDUNGEN.DOC
          Storded Size: 346.541
        Segment Number: 1/1
          Cached Copy?: No

            Node Name: NODE29
                  Type: Bkup
        Filespace Name: WINDOWS95
Client's Name for File: \USER\DATEN\WORDD\DISS TODAY\ABBILDUNGEN.DOC
          Storded Size: 360.977 ( >>> uncompressed filesize 1436 kB <<<
)
        Segment Number: 1/1
        Segment Number: 1/1
          Cached Copy?: No


   Q OCC STG=7331-POOL

   NODE29               Bkup   WINDOWS95   7331-POOL    2       0.00

You are right, ADSM has many  points of view.



Tony Pietrusiewicz wrote:
>
> 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.