For the native OSA addresses, we were using 104, 105 and 103. For our VSWITCH we used 109, 10A and 10B. z/VM TCPIP uses 10C, 10D and 10E.
From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Scott Rohling Sent: Monday, August 09, 2010 3:02 PM To: [email protected] Subject: Re: Interesting OSA problem Hmm -- seemed to start with the microcode update ... Have you rechecked your OSA values at the HMC since the microcode update? Make sure they are right speed, mtu - etc... You didn't say if your vswitch is connected to a different OSA, but am assuming it is? Doesn't make sense at first glance ... but it all depends on what the 'bad OSA' is connected to -- any chance there were also network changes to switches/routers/etc that might explain? Things like MTU size difference can cause slowness and hangs.. Scott Rohling On Mon, Aug 9, 2010 at 3:50 PM, Daniel Allen <[email protected]<mailto:[email protected]>> wrote: We are running a z9BC with z/VM 5.4. Prior to the microcode upgrade a week ago Saturday, our OS/390 guest used native OSA addresses and our z/OS guests (1.4 & 1.5) used a VSWITCH. After the microcode upgrade, our OS/390 guest (using native OSA addresses) was communicating very slowly with a TN3270 terminal. We also tested one of our z/OS (1.4) guests using native OSA addresses and communication with a TN3270 terminal was also very slow. When I put the z/OS (1.4) guest back to using the VSWITCH, everything is fine. The microcode level is 67. Over a year ago, we replaced the OSA card because of another problem. Is the OSA card having problems ? Is the VSWITCH doing something to make older operating systems work ?
