Re: STRPASTHR via ANYNET -- MIDRANGE-L

Subject: Re: STRPASTHR via ANYNET
From: Sean Porterfield <sporter@xxxxxxxxxxxx>
Date: Fri, 22 Jun 2007 19:44:52 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Michael Ryan wrote:

No, but I believe SIGNOFF ENDCNN(*YES) will do it. So, if the SIGNOFF
command was 'smartened up' to do an ENDPASTHR if it was a passthru
session, or use ENDCNN(*YES) if it was TELNET, then there wouldn't
have needed to be a change.

Yep, way back (as opposed to way, way back) we had some users on one
system that needed to get to another - due to the inability at the time
to connect directly. On the target system, we modified their signoff
option to see what the IP address was. If it was the address of the
other server, we changed to ENDCNN(*YES). We didn't want to default
that; it's quite disconcerting on a dumb terminal or PC session.
--
Sean Porterfield

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: STRPASTHR via ANYNET , rob

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