1. Forum
  2. Usenet
  3. COMP.TERMINALS

  • How can I use PuTTY with a mainframe over telnet?

    From dhdurgee@gmail.com@21:1/5 to All on Thu Oct 6 13:20:03 2016
    I am trying to figure out how to use PuTTY to communicate with a mainframe over telnet when the mainframe sends its responses with mark parity set. Needless to say these are completely unreadable in the PuTTY window. Were this a serial connection I
    cound specify "-sercfg 9600,7,m" but that is rejected for a telnet connection.

    How can I get that leading mark parity bit ignored so I can read what the mainframe is saying?

    Dave

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lorinczy Zsigmond@21:1/5 to All on Sat Oct 15 07:59:42 2016
    I think it's not about mainframe or minicomputer,
    it's about serial line (aka RS232C) instead of TCP/IP.

    I guess you could try to change settings in 'Putty Configuration /
    Connection / Serial'

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lorinczy Zsigmond@21:1/5 to All on Sat Oct 15 08:07:19 2016
    Or, it is also possible that you do use TCP/IP (not serial line),
    but the remote server uses manufacturer-specific
    protocols/terminal-sequences (such as SNA and telnet-3270).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?L=c5=91rinczy_Zsigmond?=@21:1/5 to Lorinczy Zsigmond on Sat Oct 15 18:40:58 2016
    On 2016.10.15. 8:07, Lorinczy Zsigmond wrote:
    Or, it is also possible that you do use TCP/IP (not serial line),
    but the remote server uses manufacturer-specific
    protocols/terminal-sequences (such as SNA and telnet-3270).

    Or EBCDIC.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Bob Butler@21:1/5 to dhdurgee@gmail.com on Thu Oct 27 06:09:54 2016
    Mainframes don't use serial communications historically. Telnet won't work
    for a traditional mainframe running z/OS and prior. However it will probably work if you are trying to connect to a UNIX or Linux instance running on a mainframe.

    If you're trying to work with the traditional z/OS OS or prior versions then you'll need a tn3270 client. x3270 is a good, free implementation.

    On 2016-10-06, dhdurgee@gmail.com <dhdurgee@gmail.com> wrote:
    I am trying to figure out how to use PuTTY to communicate with a mainframe over telnet when the mainframe sends its responses with mark parity set. Needless to say these are completely unreadable in the PuTTY window. Were this a serial connection I
    cound specify "-sercfg 9600,7,m" but that is rejected for a telnet connection.

    How can I get that leading mark parity bit ignored so I can read what the mainframe is saying?

    Dave

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Kaz Kylheku@21:1/5 to Bob Butler on Thu Oct 27 15:10:54 2016
    On 2016-10-27, Bob Butler <bob@work.com> wrote:
    Mainframes don't use serial communications historically. Telnet won't work for a traditional mainframe running z/OS and prior. However it will probably work if you are trying to connect to a UNIX or Linux instance running on a mainframe.

    Async serial: too cheap, simple and standardized for mainframes.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jeff Jonas@21:1/5 to All on Thu Nov 24 00:47:22 2016
    Mainframes don't use serial communications historically.

    Async serial: too cheap, simple and standardized for mainframes.

    Mainframes did SDLC sync-serial for remote terminals / RJE (remote job entry). Zilog's serial chips handled that in hardware.

    There used to be many makers of protocol converters
    from mainframe SNA to plain RS232 terminals and modems.
    Similar to terminal servers to Token Ring, Ethernet, Decnet, etc.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Scott Dorsey@21:1/5 to Jeff Jonas on Thu Nov 24 08:03:12 2016
    In article <o15uta$3ca$1@panix3.panix.com>, Jeff Jonas <jeffj@panix.com> wrote: >>> Mainframes don't use serial communications historically.

    Async serial: too cheap, simple and standardized for mainframes.

    Mainframes did SDLC sync-serial for remote terminals / RJE (remote job entry). >Zilog's serial chips handled that in hardware.

    Which was a smart thing, since handling error correction and block stuff
    at the data link layer then became possible. Much more reliable than just opening up a port and jamming data through and hoping for the best when it appeared on some screen halfway across the country.

    The mini folks first started using async serial so they could take advantage
    of cheap teletype consoles.

    There used to be many makers of protocol converters
    from mainframe SNA to plain RS232 terminals and modems.
    Similar to terminal servers to Token Ring, Ethernet, Decnet, etc.

    I believe that a bisync-to-async box was the first actual product that an
    8051 was used in. Later ones got even smarter and many were available
    that supported IBM and Burroughs block terminal protocols and translated
    to vt100 sequences.
    --scott


    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)