Just a comment - It seems like it would be useful to get a report of the
numbers of versions of each file in a filespace.  Since we have a pretty
liberal policy of keeping unlimited versions for 600 days, I would like
to see if there are any "abusers" or files with an ungodly number of
versions that we really don't need.

Ron Clendenny  <rdclendenny AT cal.ue DOT com>
Callaway Nuclear Power Plant
Fulton, Missouri

"The difference between a madman and me is that I am not mad" - Salvador
Dali

>-----Original Message-----
>From:  Dianne Sharp [SMTP:DSHARP AT CLEAR.CO DOT NZ]
>Sent:  Tuesday, March 18, 1997 7:08 PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: Query Occupancy question
>
>That's what I thought.  Thanks for the confirmation.
>
>Dianne Sharp
>Operations Analyst
>CLEAR Communications, Auckland, New Zealand
>dsharp AT clear.co DOT nz
>>----------
>>From:  Dave Cannon[SMTP:dcannon AT VNET.IBM DOT COM]
>>Sent:  Wednesday, 19 March, 1997 11:48AM
>>To:    ADSM-L AT VM.MARIST DOT EDU
>>Subject:       Query Occupancy question
>>
>>>When you use the Query Occupancy command to see how much space on the
>>>server is taken up by a particular node, it tells you how many files for
>>>each file space.
>>
>>>Does this number inlclude muliple backup versions of a file?  i.e. if
>>>there are 20 files in the filespace and you are keeping 2 versions of
>>>each, will this figure be 40?
>>
>>The value in the Number of Files field is the number of objects that occupy
>>space in the indicated storage pool.  Each version of a file is considered
>>to be a distinct object, so would be counted separately.  In your example,
>>the value would be 40.
>>
>>Dave Cannon
>>ADSM Development
>>