Finally I can close this problem. PC is back in data center and connected to the ICC. Still don't know what was the root cause. I guess alls well that ends well. Since a rework of the pc fixed the problem I guess it's safe to say that it was the culprit although there was absolutely no evidence to support it. One of the odd things I did notice on the mainframe side was the fact that dropping a session in the icc debug panel on the hmc didn't result in what I would expect. Even though the session shows available after the drop the mac & ip address remain from the previous session. No biggie but good to know. Another thing that came up during this which makes me wonder is microcode. Is it true that varying off/on the chpid could cause any newer microcode waiting to be loaded? Would a power on reset also have the same effect? The way it was explained to me (by IBM) is that microcode is automatically downloaded to the mainframe as it becomes available. It is then loaded as I previously noted. Thanks again for the help. -Jim
On 9/13/07, Alan Altmark <[EMAIL PROTECTED]> wrote: > On Thursday, 09/13/2007 at 12:41 EDT, James M <[EMAIL PROTECTED]> wrote: > > I'm now wondering if there are certain emulators that are better than > > others. Does IBM support/recommend certain emulators? > > Here I am blaming the emulator - maybe I should be considering a linux > > based icc console. > > IBM sells its own emulator, IBM Personal Communications (PCOMM). However, > it would be hard to say that IBM "recommends" any particular emulator in > this respect, however, since telnet is an open standard. If ICC isn't > operating according to the RFCs, then we'll fix it. > > > Getting back to the pcap file - it looks like there was about 10 > > seconds elapsed from act to fin. If you really want I can send the > > pcap file. If so let me know where to send it. > > At this point the question is moot. The 10-second delay confirms, I > think, that the ICC was waiting for the WILL TN3270E from your PC. After > 10 seconds with no response from your PC, he [appropriately] closed the > connection. > > Alan Altmark > z/VM Development > IBM Endicott >
