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?   

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
Thompson, Steve
Sent: Thursday, June 18, 2009 11:13 AM
To: [email protected]
Subject: Re: TCP Settings for KeepAlive

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of Hal Merritt
Sent: Thursday, June 18, 2009 10:20 AM
To: [email protected]
Subject: Re: TCP Settings for KeepAlive

Hmmm.. almost sounds like QWS3270 may be getting impatient when waiting
for a reply. That is, the 'keep alive' time may apply only to an idle
session as opposed to a wait for reply situation.  

I'd look into QWS3270 parameters. 

<SNIP>

QWS3270 is the one getting notified that the connection has dropped. In
discussions with Jolly Giant, they will wait forever for the host to
respond. Meanwhile, they will continue, at the prescribed intervals, to
send the keepalive.

Something, somehow is deciding on the host side to terminate the
connection. And I just can't seem to find it.

Regards,
Steve Thompson

----------------------------------------------------------------------
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
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

----------------------------------------------------------------------
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

Reply via email to