• Subject: RE: inactive time-out on telnet
  • From: "Martin, Booth" <BoothM@xxxxxxxxxxx>
  • Date: Mon, 8 Nov 1999 14:40:58 -0500

oh, that makes sense.  What I did here was to build a new subsystem for
telnet only.  All telnets come to this subsystem, only.  It has it's own
screen an 'everythin'.  But then we can shut down the subsystem and start it
at will.  (Telnet users seem to keep weird hours.)

-----Original Message-----
From: Terry Richardson [mailto:RichardsonT@orvis.com]
Sent: Monday, November 08, 1999 1:36 PM
To: boothm@goddard.edu
Subject: RE: inactive time-out on telnet


Booth-
        Technically, just the jobs.  We accomplish this on the SNA and green
screens via the QINACTITV system value.  The time mark time out value in the
telnet attributes tells the session to signal the 400, effectively making
the job appear as 'active'.  At least, that's what I've been able to glean
from the archives of midrange-l.  It would explain why these sessions never
die.  

Terry Richardson
Sr. P/A
The Orvis Company, Inc.
802-362-8663


        -----Original Message-----
        From:   Martin, Booth [SMTP:BoothM@goddard.edu]
        Sent:   Monday, November 08, 1999 12:16 PM
        To:     'MIDRANGE-L@midrange.com'
        Subject:        RE: inactive time-out on telnet

        Terry, which do you need to close?  The telnet sessions, or the
jobs?  

        There'd be no reason to close down sign-on screens since no
production files
        are locked with just a sign-on screen up.  What I am driving at is
that I'm
        thinking you want to shut down jobs, not telnet connections.  The
problem
        you describe of locked files would happen whether they are on Client
Access
        Express, SNA, or a regular twin-ax line wouldn't it?
        +---
        | This is the Midrange System Mailing List!
        | To submit a new message, send your mail to
MIDRANGE-L@midrange.com.
        | To subscribe to this list send email to
MIDRANGE-L-SUB@midrange.com.
        | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
        | Questions should be directed to the list owner/operator:
david@midrange.com
        +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 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.