Hi Chris, I'm still reading your reply to the Attachmate tech-note link that I gave you, but I thought that it's important to let you know that the only change we made is what's documented below:
Enabling Keep-alive Support in EXTRA! To enable client-initiated keep-alive support, you must configure EXTRA! to use the Microsoft TCP/IP KeepAlive parameter. Follow these steps: 1. Close any open EXTRA! host sessions. 2. In a plain text editor, such as Notepad, open the EXTRA! session configuration or EDP file you are using for the TN3270 session. (To enable the KeepAlive parameter in all newly created TN3270 sessions, modify the 3270.EDP file.) By default, this file is located at C:\Program Files\Attachmate\EXTRA!\Sessions\ENU\Template\3270.EDP. 1. In your EDP file, scroll down to the [Connection] heading. 2. Add the following line to the [Connections] section. KeepAlive=YES Or, to disable this feature (the default), delete the line or change the value to NO. KeepAlive=NO 1. Save the file. 2. Restart EXTRA!. We did NOT make the registry change, so I'm assuming that the default of 2 hours is in effect. From the little I've read from your response, this is NOT a good thing. Is it possible for you to provide any information on the firewall settings and what to look for or what's not specified that could be causing this 2 minute disconnection problem? Again, I truly appreciate all the help you've provided. * * *George Rodriguez* *Specialist II - IT Solutions* *Application Support / Quality Assurance* *PX - 47652* *(561) 357-7652 (office)* *(561) 707-3496 (mobile)* *School District of Palm Beach County* *3348 Forest Hill Blvd.* *Room B-332* *West Palm Beach, FL. 33406-5869* *Florida's Only A-Rated Urban District For Six Consecutive Years* On Mon, Feb 14, 2011 at 11:55 PM, Chris Mason <chrisma...@belgacom.net>wrote: > George > > I'm pleased to see that you report having solved your problem and I'm sorry > for the delay in responding to your numerous posts of a fortnight ago. You > may have noticed some of the aggression with which I have had to deal in > the > last few days - and it continues - but you deserve the responses I've been > getting ready. > > In order to understand what I am about to cover, you will need to read over > my response to your post where you asked me to analyse the Attachmate > article which, in essence involves introducing TCP-level "keepalive" > processing > in the TCP support in the Microsoft Windows workstations supporting the > Attachmate TN3270 client. > > Since you report you have solved your problem by introducing TCP > "keepalive" > processing in the TN3270 client, I have the following 4 points to make: > > 1. TCP "keepalive" - or its application-level equivalent - can only solve > the > sort of "timeout" problem you reported initially by, as it were, keeping a > firewall happy so that it does not decide to terminate TCP connections. The > other role of "keepalive" is to detect the death, real or apparent, of a > partner > in a TCP connection so that the local end of the TCP connection can be laid > to rest! You haven't expressed a need for this capability of "keepalive". > > 2. Presumably you have decided on a value other than 2 hours for the > KeepAliveTime Windows registry parameter so it would be useful to know what > value, time interval, you have chosen. > > 3. Assuming the value is, say, 10 minutes (600000), as a means of > satisfying > the firewall rules, you could have specified a value of 600 (10 minutes) > for the > TIMEMARK statement and, say, 300 (5 minutes) for the SCANINTERVAL > statement in the TN3270E server PROFILE data set. I imagine that would be > easier than deploying the Windows registry change and adjustment to the > Attachmate EDP file out to all your external clients. > > 4. There is an alternative or a complement to 3 which is to check what the > firewall rules are which apply to your TN3270 service IP addresses and > server > port number, 23. You should, of course, ensure that the TIMEMARK frequency > is less than the "lack of activity" timer in the firewall rules. > > - > > So, if your problem had been to "clean up" lost TCP connections in the > workstations supporting your Attachmate clients, you have done the right > thing by deploying the customisation described in the Attachmate article. > > However, since your problem was to avoid disconnections of the TN3270 > traffic, it is very probable there were two much easier ways to solve the > problem - but it's your choice. > > Chris Mason > > On Fri, 28 Jan 2011 07:48:58 -0500, George Rodriguez > <george.rodrig...@palmbeachschools.org> wrote: > > >Chris / Patrick, > > > >The tech-note in Attachmate's database did solve the timeout problem. > Thanks > >again for the help... > > > >*George Rodriguez* > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > Home of Florida's first LEED Gold Certified School Under Florida law, e-mail addresses are public records. If you do not want your e-mail address released in response to a public records request, do not send electronic mail to this entity. Instead, contact this office by phone or in writing. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
