× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Jon,

I, too, have written my own Telnet client. But, it has been many years, and I do not have the telnet negotiation codes memorized. I suspect you'll have to go look them up in the RFCs.

The other thing to consider here is the terminal emulation that's in use here. Telnet itself is only a starting point, and the Telnet standard only defines a simple NVT terminal. From there, you are supposed to upgrade to another terminal emulation type such as ASCII terminals like VT220, or EBCDIC ones like the 5250 or 3270.

Stuff like "line mode" seems like it'd be more closely related to the terminal emulation than the telnet protocol itself... at least, that's what I remember (but my memory is quite fuzzy).

-SK




On 12/5/2012 8:54 AM, Jon S wrote:

All,

I wrote my own Telnet Client in RPG several years ago and I have been asked to change it from character-at-a-time to line-at-a-time mode. I am sure this is done in the negotation string that I send back to the host. The following is what I received from my customer:

"There is an understanding known as kludge-line mode, which means that if either "suppress go ahead" or "echo" is enabled but not both, then Telnet operates in line-at-a-time mode."
I am not sure how to do this. Currently I am sending back
request = X'FFFE03+
FFFE01' + CRLF2
but it's been so long ago that I don't even remember what that means.

Can anyone help me out?

Thanks, Jon


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.