If a 10 Mb pipe is all you have, set compression ON !
     also set tcpnodelay ON
     I take it your connection into MVS is not an OSA adapter...
     Make sure your MVS performance folks are giving adsm enough cpu
     cycles... you can kill adsm on mvs if it is tuned wrong.

     I have an AIX server that accepts 25 GB/hr from a single client so it
     can perform very well, thus it can grow with your needs.

     In our testing our current bottle neck in our slowest activity is the
     client dasd during a retrieve of an archived data base... this is due
     to the time spent writing the "mirrored" file once it gets to the
     client.  We can speed up the recovery time by turning off mirroring
     during the restore but that is just putting off paying the piper ;-)

     just some misc info
     later,
            Dwight


______________________________ Reply Separator _________________________________
Subject: transfer speed
Author:  dbrown at unix,mime/DD.RFC-822=dbrown AT TELALINK DOT NET
Date:    2/10/99 2:53 PM


We purchased ADSM in hopes of getting rid of ArcServe and 4mm tapes. In
order for us to keep it, we have to prove that ADSM is going to be at least
as fast as ArcServe. So far, I haven't been able to pull it off. I thought I
would ask the list what kind of transfer rates they (you) were getting. I
realize that there are about a million factors that can have an effect on
the rate, so I'm really only looking for some good ballpark figures, but
even that may not be possible.

Here's the setup...

133Mhz Pentium, NT server with 100+ MB RAM and a 10Mb pipe. Compression is
off and all setting are at optimum per the "Performance Tuning Guide". Data
passes from the server (client) to a router, then out of the router into the
mainframe (S/390) in the next room. Again, a 10Mb pipe all the way. ADSM is
v3r1. Should I be getting better than 575-600K/sec?

Thanks for any help.

--
Doug Brown
Doug Brown

21F3 8086 1D2D 5ED0 1794  2ED9 CFC3 8043 928B 6551