Rick, As Fritz has mentioned, you need Anynet to get the SNA over TCP/IP support that SNADS needs. Another way to end your host-to-host telnet passthru is to use the ENDCNN(*YES) option of the SIGNOFF command. On the systems I deal with, I've created a CL command that does SIGNOFF ENDCNN(*YES). An additional benefit is that this command will also end a host-to-host STRPASTHR terminal session (display station passthru). When I'm done with my remote session, I just type EP (my command name) and I'm back to my home system without having to remember if I used TELNET or STRPASTHR originally. This also helps if I have to telnet to one system (let's call it A) and then telnet to still another (let's call it B). Using my EP command on system B returns me to system A. If I'm on system B and use the ATTN key and option 99, I drop all the way back to my home system. A way around that using the ATTN key would be to use option 5 (Attn key to remote host). Doing that would display the "Send TELNET Control Functions" for system A. Hope this helps! Richard -----Original Message----- From: Rick Rayburn [mailto:email@example.com] Sent: Tuesday, December 04, 2001 10:57 AM To: firstname.lastname@example.org Subject: RE: APPC - TCPIP Communications - SNADS Thanks to all who have helped in establishing our connection. We can Tele-net as a Passthru means (can the strapasthr command still work though?) but what about SNADS? Anyone know? Also, does anyone have any Tele-net session ending information (a la endpasthru?)
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.