|
Yes thanks, John. It was a combination of the setting of these 2 parameters. The key, from a previous post, was to set the TIMMRKTIMO significantly greater (3 to 5 minutes) than INACTTIMO. I am now happily annoying my users again. Dave Kahn, TCO, Kazakstan ========= kahn@tengizchevroil.com (to November 25) dkahn@cix.compulink.co.uk (from November 26) >-----Original Message----- >From: John Earl [SMTP:johnearl@lns400.com] >Sent: Friday, 14 November, 1997 12:42 >To: MIDRANGE-L@midrange.com >Subject: RE: QINACTITV on TELNET sessions? > >Dave, > >At 09:35 PM 11/8/97 +0500, you wrote: ><snip> >> >>On a related note, we are just switching to the dreaded NT desktops and >>are using the Client Access 5250 emulator over Telnet. The sessions are >>not timing out after they reach the Telnet inactivity timeout limit. Has >>anyone else experienced this, and do they know why? The Rumba sessions >>under Win 3.1 always used to timeout correctly. > > >This is sort of an odd bird, but if you set the telnet inactivity >(INACTTIMO) to a value greater than 600 seconds, it _appears_ not to work. >That's because the parameter just below INACTTIMO on the CHGTELNA command, >TIMMRKTIMO causes the /400 to send a 'keep alive' message to the telnet >partner every 600 seconds (the default). That keep alive message seams to >cause the telnet INACTTIMO interval to get reset. > >If you set INACTTIMO value to, say 3600, and then the TIMMRKTIMO value to >something greater than 3600, your telnet sessions will time-out. > >They time-out ugly though. Instead of reverting to the signon screen, my >Rumba sessions go blank with the curser at 1/2. A simple disconnet and >reconnect causes a signon screen to reappear. > >hth, > >jte > > > >********************************* >* John Earl * >* Lighthouse Software Inc. * >* 8514 71st NW * >* Gig Harbor, WA 98335 * >* 253-858-7388 * >* johnearl@lns400.com * >********************************* > > > >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to "MIDRANGE-L@midrange.com". >| To unsubscribe from this list send email to MAJORDOMO@midrange.com >| and specify 'unsubscribe MIDRANGE-L' in the body of your message. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- >umidr +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.