>> Logon reconnect doesn't usually work if you're connected with TCP/IP and >> TN3270.
> That's just a bug that IBM can't be bothered fixing. I don't consider myself an IBM apologist, but with respect to Mr. Woren, I don't believe it's an IBM problem. This problem is simple to recreate, provided you're on a Win system and using an IP terminal emulator. Pull up a CMD prompt and enter "IPCONFIG /RELEASE" You immediately lose all mainframe and IP connections. Enter "IPCONFIG /RENEW" and you can connect again. As far as the mainframe is concerned, your session is still active and waiting for input. It wasn't notified the session died. The mainframe (and by extension, IBM) couldn't know this since IP is stateless. In this case, the problem stems from DHCP leases and the DNS. The DHCP leases expire and you have to renew them. This is when your session dies. A responsible LAN admin will time the DHCP leases to expire in the wee hours of the morning. They would do this by scheduling a global RELEASE/RENEW that affects every PC on an entire LAN. (I wish we had a LAN admin like that...) It's also something individual users can do as well since many leases are specified in 24 hour increments. Enter "IPCONFIG /ALL" and see when your lease expires. Schedule a RELEASE/RENEW in the wee hours of the morning. I know there are other causes, but this is a way to reduce your exposure to session drops. Regards, Kevin Kinney ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
