Subject: | |
From: | |
Reply To: | |
Date: | Mon, 24 Mar 1997 09:29:52 PST |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Subject: Re: Connecting to a Mainframe through a LAN
Tracy Johnson wrote:
>If you don't care about losing block mode, AND if you're using MPE/iX 5.5,
>you can simply TELNET inbound using the default Windows dumb terminal
>program, you don't have to spend a dime.
>You end up emulating a VT100 or VT52.
<snip Powerhouse information deleted for brevity >
Just a quick word of caution, well ok two points of clarification, 'cause
I can never do it in a word....
First, Telnet Server on 5.5 out of the box will reject connections from
the default windows terminal emulator. You need 5.5 Power Patch 1 to have
this work. The issue has to do with telnet option negotiations. We didn't
catch it until after submitting to the MIT.
Second, Telnet Server/iX does term type 10, ie HP terminal behavior only.
Therefore we send the D1 read trigger. The default terminal on windows
tends to display the D1 as a SPLAT (for lack of a better technical term).
This looks bad on your display, but so far as I know doesn't mess up any
CI type functionality. If you write an application that reads the screen,
you should look into using FDC 192,30 (see the Asynch Programmer's
Reference Manual for details) to disable the read trigger. Of course we
only support Telnet/iX Server with clients doing HP terminal emulation.
So technically using the default windows terminal emulater is
unsupported.
Hope this is helpful.
cas caswell
HPCSY Lab
--
=======================================================================
[log in to unmask] (Cas Caswell) By the way: I said it, not my company.
=======================================================================
|
|
|