Yes, the common item to this problem is the Session manager. We were just discussing this among ourselves just a few minutes ago.
If QWS is connected directly to the TSO APPLIDs (as opposed to going through the session manager first), then these timeouts do not happen. However, because of a few other things that were discussed, I am starting to think there is a problem with QWS. The problem is, proving what is the problem and how to solve it. Regards, Steve Thompson -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Hal Merritt Sent: Thursday, June 18, 2009 11:25 AM To: [email protected] Subject: Re: TCP Settings for KeepAlive True: we are searching for what drive the lost session disconnect. But I would not limit my search to the host. Network appliances/firewalls can be configured to do things like this. What does not fit in this scenario is that other TN3270 clients are not having the problem. That would point back to QWS as being the unique factor in the equation. That said, we cannot assume that all are following the same network path (and thus chain of network appliances/firewalls). Another thought: Have you tried connecting directly to the host and bypassing the session manager? <SNIPPAGE> ---------------------------------------------------------------------- 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
