Hi, Perry. Our installation has similarities and we did some tuning this
summer. The only parameters where we got any significant performance increases
were from the Datapoolbuffersize and the TCPWindowsize. We have both of them
set to 32k. Supposedly TCPIP negotiates its windowsize between the client and
the server stack, picking the lower of the two. That would be 32k in your
case. Increasing the Datapoolbuffersize to 64k may help. We were unable to do
this in our environment because we share the stack.

I saw that someone else suggested adjusting the TXNBytelimit and the
Maxtxngroup, but we found this a trade off and saw no measurable performance
gains. We run at 2048 and 40, respectively.

Good luck,
Dennis





 (Embedded
 image moved   pmcgrew @ AGWAY.COM
 to file:      12/10/97 04:47 AM
 PIC32765.PCX)




Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L @ VM.MARIST.EDU
cc:    (bcc: Dennis Riley/BLLVRLNS3/USWEST/US)
Subject:  Tuning tips?




We've just installed ADSM/MVS 3.1 on our TCP/IP 3.2 Ethernet network
over ATM (LANE) backbone.  We have the lastest ADSM 3.x client code on
our HP-UX 10.2 & IBM AIX 4.3 servers.
In the dsmsched.log I am seeing:
Network data transfer rate:        1,772.97 KB/sec
Aggregate data transfer rate:      1,468.25 KB/sec
We do not have ADSM compression turned on as we are using hardware
compression on our 3494/3590 MagStar tape drives.
Our TCPIP/MVS 3.2, the  LARGEDATABUFFERPOOLSIZE is set to 32768.
In the HP / AIX Clients' the dsm.sys parameters are:
   TCPWindowsize      64
   TCPBuffsize             32
   TXNBytelimit       2048
Any help in identifying critical tuning points will be appreciated!
Thanks,
Perry McGrew
Agway Inc.