> TSM v6 server on Linux or AIX will forward data to the z/OS TSM media > server via TCP/IP. If you have TSM in a Linux LPAR or guest on the same CEC > with z/OS, it can use HiperSockets to stream the data to z/OS.
Caveat: it's a good idea to look *very* carefully at how you configure WLM to ensure the TCPIP stack in the z/OS that is used by the TSM media server both gets enough resources to do the job and also doesn't use so much horsepower as to take over the system. You're going to be moving a LOT of data through that stack, and that will chew up resources very quickly. If you have to run it in the same z/OS as your regular work, think very hard about running a second TCPIP stack for just that one purpose; it's easier to control the behavior. The TCP stack tuning parameters that work well with the TSM media server (large MTUs, large packet sizes, long TCP windows) are not friendly to interactive terminal traffic, so as noted above, it's a good idea not to share the stack supporting the terminal users with the TSM media server. Like TSM itself, the media server benefits from jumbo packets, long frame sizes and long packet sizes with minimum fragmentation; a separate TCP stack is the easier way to implement those characteristics. Also, make sure you take some baseline readings with your performance monitor before and after implementing the TSM media server. Tuning the network for this purpose is somewhat of a trial and error thing, and you'll want the data to see what changed. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
