RE: Ending TELNET sessions.... -- MIDRANGE-L

Hello Doug,

I am still thinking about a way to handle this.  I have not managed to find any 
API or other method which 
would reliably provide this information.

Netsoft is TELNETing to the AS/400 therefore ENDCNN(*YES) is behaving properly. 
 A couple of things I have 
thought of:

1) Run TCP from the workstation to the AS/400 but run SNA between the AS/400 
and use DSPT.

2). Check the *DEVD for the workstation and check the value for DROP (?) since 
LANs are effectively switched 
connections.  (SIGNOFF has DROP(*DEVD) as the default action.)

Regards,
Simon Coulter.

//----------------------------------------------------------
// FlyByNight Software         AS/400 Technical Specialists
// Phone: +61 3 9419 0175      Mobile: +61 0411 091 400
// Fax:   +61 3 9419 0175      E-mail: shc@flybynight.com.au
// 
// Windoze should not be open at Warp speed.
//--- forwarded letter -------------------------------------------------------
> X-Mailer:  Microsoft Exchange Server Internet Mail Connector Version 
>4.0.995.52
> Date: Thu, 08 Oct 98 13:48:41 -0400
> From: "Hart Doug" <dah6696@Goulds1.com>
> To: "MIDRANGE-L@midrange.com" <MIDRANGE-L@midrange.com>
> Reply-To: MIDRANGE-L@midrange.com
> Subject: RE: Ending TELNET sessions....

> 
> 
>       The command SIGNOFF ENDCNN(*YES) looks to be the simple answer but I
> would like to take this a step further.  I use Netsoft's TCP
> connectivity from my desktop to an AS/400.  If I signoff the AS/400 with
> ENDCNN(*YES) it drops me out to a black window and I must reconnect to
> get back to a 400 signon screen.  The problem comes when I tried to
> enhance my custom signoff program.  We like most shops with multiple
> system have a modified signoff program that in some form does an
> ENDPASTHR.  This is quite handy when exiting a second (passed through)
> system.  Now to telnet.  The signoff endcnn(*yes) works well on a second
> system as well, but not from your primary PC to 400 session through
> Netsoft TCP as mentioned above.
> 
>       So the issue becomes how do I know if I'm on my 2nd AS/400 hop via
> telnet vs. my primary system so that I can execute signoff with or
> without ENDCNN?  The trick seems straight forward.  When I hop to a
> second 400 via telnet and hit <esc> I get the  menu 'Send TELNET Control
> Functions'.  This does not show when I'm attached to the primary AS/400.
>  Now how do I test for this menu or function?  Nothing different shows
> in the program stack from on system to another.  Does anyone know of an
> API that has a flag?
> 
> ---
>   Douglas Hart - Sr. Consulting Technical Analyst
>   ITT Fluid Technology / Goulds Pumps
>   240 Fall Street
>   Seneca Falls, New York  13148
>   (315)568-7568 Voice   (315)568-7129 FAX
>   mailto:dah6696@goulds1.com 
> 
> 
>      I know this came up not too long ago, but I didn't need to know 
>      then... :)  As I recall, the consensus was that the only way to end
>      a TELNET session to another as400 is to use the attn 99 disconnect 
>      option. Is that correct, or is there some command comparable to 
>      ENDPASTHR for ending TELNET?
>      
>      TIA
>      eric.delong@pmsi-services.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
+---