Dave,

am I right saying that instead of using this new option NOAGGREGATES, I
can simply use the parameter

TNXGROUPMAX  1, instead of the default value of 256

in the server option file? This should force an aggregate of 1 !

Thanks,

René Lambelet - (3543 - *A581 
Nestec SA - 55, Av. Nestlé - CH-1800 Vevey
Tél: ++41/21/924'35'43 / Fax: ++41/21/924'45'89
E-Mail: rene.lambelet AT nestle DOT com



>-----Original Message-----
>From:  David Cannon [SMTP:cannon AT US.IBM DOT COM]
>Sent:  Tuesday, April 07, 1998 11:09 PM
>To:    ADSM-L AT VM.MARIST DOT EDU
>Subject:       Re: AUDIT RECLAIM Utilities
>
>>Andy, The reclamation utility function is not available yet.   In our
>>announcement Friday, April 3rd it was explained that our reclamation
>>                utilites will be made available soon.  The server you are
>>running supports the new (temporary) option NOAGGREGATES
>>                which disables file aggregation.  One good reason to use
>>this
>>option is to limit the number of ADSM aggregates
>>                 the utilites will have to process.
>
>
>As stated above, the utilities are not yet available.  However, the above
>post
>also suggests that using the NOAGGREGATES option will reduce the amount of
>processing that the utilities will need to perform.  This is not true.  In
>fact, using this option will increase the processing that must be performed
>by
>the utilities.  Probably the only real reason to use the NOAGGREGATES option
>would be if you are running short of tapes and cannot afford to leave empty
>space within aggregates after reclamation has been performed.
>
>To repeat, do not use the NOAGGREGATES option with the expectation that this
>will reduce the amount of time required to run the utilities.
>
>Sorry about the confusion.
>
>Dave Cannon
>ADSM Development