One that tends to happen with network groups that report to a different management than the Mainframe people is that they like to try to "replace" functionality that is already built-in to things on the mainframe like OSA, so they will add "smart" switches and routers that try to do things that conflict with what you OSA normally can handle internally between your LPARs, which tends to manifest itself as slow response time for some things.
Since it's just FTP for you, then it's likely that they have implemented either some changed buffer sizes or (even worse) they may have left trace turned on for something. There are some really good products that are really good to have on the mainframe, like service pilot, which allows you to trace what's happening from the inside of the mainframe outwards to the network. The network people tend to have some really cool tools on their end, but the mainframe is a black box to them, which is the same way that their network looks to the mainframe, so having something on your side that can be used by them (and you) to monitor the throughput is a really good idea. I think service pilot even has a "freeware" part that you can use for a while to see if you like it. You might wnat to give it a try as you are in a situation where it might be exactly the tool you need to see where the problem is. I think their site is www.servicepilot.com. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
