I would say that the problem almost definitely lies in the realm of the qeth and qdio drivers. As I mentioned before, starting the newtwork after removing the qeth and qdio modules did initially clear my problems up. Simply restarting the network wasn't sufficient, the modules had to be removed. I've also noticed that I can log into a machine via the console and it responds normally. Unfortunately, I don't think that my users will consider the mandatory use of x3270 and ed as any kind of real solution.
Your desription of the similar problems that you are experiencing makes them sound intermittent in nature. Is that so? As I said, all of my machines are constantly exhibiting this behavior. The difference lies in the severity of the delay. If a machine is terminally fouled up, I've found that bouncing the network and reloading the qeth/qdio drivers can help, but doesn't bring it back to the responsivity level that we enjoyed under z/VM 4.2. "Improvement" means the delay between keypress and display lasts 1-3 secs. rather than 4-8 secs. So far, our network services haven't been too adversely effected on images that are experiencing the minimal delay. On the machines that are begging for a network bounce, however, there is a noticable delay, sometimes painfully so. Oviously, this is an untenable situation. One final question: Are these problems that I'm experiencing a side-effect of our upgrade to 4.4, or is it something only peripherially associated with it? Thanks for the responses, Michael Lambert >There are definitely some problems in this area, but I'm not sure how to >isolate them. The folks that run the LCDS seem to think it is with the >qeth/qdio Linux/390 drivers. I see symptoms very similar to what you're >seeing. Random, moderately frequent network "freezes" that clear themselves >anywhere from 1 to 20+ seconds (or more?). > > >Mark Post
