Does the MVS box talk to the  world via a 3172 interconnect controller
     (I think that's the right number) or does it have an "open system
     adapter" (OSA) ?

     To move any data you'll need to use the OSA... run two tcp's under
     mvs, have one talk to users, the other talk to adsm clients (each with
     its own hardware, network interface wise). You can tune the tcp/ip's
     much better that way.

     If you're not sucking the MVS processor dry of cpu cycles then you
     need to improve the door into mvs.

     Or just start building AIX adsm servers on S-70's with 3494-L12's &
     3590's... then as the client environment grows to exceed the single
     adsm server, add another.  You get to utilize the existing 3494 by
     just adding a drive cabinet & some more drives.

     We've just started in the the S-70's but with an R-50 and archives it
     would take 3 clients each having two different network connections
     into the adsm server, all the networks being different (ie 6 fddi's
     into the adsm server) and each client running 18 concurrent archive
     sessions with compression turned on to max the adsm server.  So if my
     brain hasn't shorted out yet, I believe the figures came out to 100+
     GB/hr inbound archives with client compression  thus that was 200+
     GB/hr of client data.  That is if the clients has enough CPU to handle
     the disk I/O and compression activity


______________________________ Reply Separator _________________________________
Subject: Help
Author:  roecken (roecken AT ca.ibm DOT com) at unix,mime
Date:    7/21/98 8:38 AM


Hi, I was wondering if anyone could give some suggestions on this one.  Thanks.


A client is currently backing up to their Host using ADSM but due to increases
in the amount of data they are missing their backup window.  They are looking
at improving their throughput.

Current Environment:
 ADSM/MVS Server on OS/390 with TCP/IP
 7 Node none-switched SP and standalone servers (the 7 nodes are both
Thin and Wide MCA bus Nodes)
 All systems are attached to the Host via a Token-Ring network

Client's Plan
 Add additional devices to their Host system
 Place an ESCON Channel adapter in one of the Wide Nodes in the SP for
attachment to the Host
 Place a Switch in the SP for inter SP ADSM backup traffic
 Possibly include an SP Switch Router with an ATM backbone for
attachment to the standalone servers

 Questions:  This creates a gateway for the ADSM product (ie: server to
ESCON Gateway Node to ADSM MVS Server).  Can this be done?  Any suggestions,
limitations, comments?

We had also suggested establishing a tape library attached to the SP complex
itself.  The client felt that politically this would be difficult to do and
preferred to maintain the route to the Host for backup.  There is contention
with Host based backups that must occur at the same time.

___________________________________________
Michael Roecken