Julie,

        Here is what we have in our OS/390 server options file:

TXNGroupmax     256
MOVEBatchsize 1000
MOVESizethresh 500

        It is correct to have the MOVEBatchsize command set to 1000.  I
went to the advanced training class, and was told despite what the
documentation says, 1000 is the max setting for this parm.  To answer
the question in your second e-mail, we have the compressalways option
set to no.  Hope this helps.

Rick Smith
Maritz, Inc.
Storage & Security Administration
smithrr AT maritz DOT com
(314) 827-1584

> ----------
> From:         Julie Phinney[SMTP:jphinney AT HUMANA DOT COM]
> Sent:         Tuesday, March 17, 1998 5:15 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      ADSM V3 tuning on MVS
>
> I am moving ADSM on OS/390 from V2 to V3. In reviewing the server
> options
> file, I noticed a couple parms that I tuned before, according to a
> Performance and Tuning Guide for ADSM, that may need revisiting now
> with
> ADSM V3 and it's small file aggregation.
> The numbers I have specified are:
> TXNGROUPMAX   40    (I seem to remember some problem, a long time ago,
> when
> I tried hiking that number to the max)
> Movebatchsize 1000     (can't remember why I did that,  the doc in the
> opt
> file says that number can only be as high as 256)
> Movesizethresh 500
>
> Are you all moving that TXNGROUPMAX up to something higher when you go
> to
> V3, to get more performance benefit from small file aggregation?
> What are you V3 users on OS/390 using for those 3 numbers?
> Does anyone know if there is a new, updated Performance and Tuning
> Guide
> for ADSM for V3?
> Thanks,
> Julie
>