RE: 3270 emulation and TCP/IP and Terminals -- MIDRANGE-L

As I recall, there are a couple vendors out there still selling 400
(opps - iSeries hardware legacy boxes).  There used to be a controller
that you could connect to a TCP/IP stream that would convert it for 5250
type devices (twinax).  I don't know the vendors, maybe someone does,
but you might look up remote controllers on search400 or one of the
other "stuff" sites.

john

John Bussert
Swift Technologies, Inc.
www.swiftorder.com
847-289-8339
847-289-8939 (fax)
jbussert@swiftorder.com


-----Original Message-----
From: Adam Lang [mailto:aalang@rutgersinsurance.com]
Sent: Tuesday, December 18, 2001 1:36 PM
To: midrange-l@midrange.com
Subject: Re: 3270 emulation and TCP/IP and Terminals

I'm not really sure how that helps.  The problem is I still have
terminals
that are connected to the AS/400 via twinax.  I need to know what I need
to
setup so that they can passthru the AS/400 to connect to the OS/390.
Currently it is done using streml3270 over an SNA line.

Apparently streml3270 only works over SNA.

So far the only lead I have is the previous post involving anynet.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: <rob@dekko.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, December 18, 2001 2:36 PM
Subject: Re: 3270 emulation and TCP/IP and Terminals


>
> Adam,
>
> The AS/400 supports telnet.  If your existing 400 has TCP/IP installed
and
> configured then it is a simple test - telnet to itself using the
command
> TELNET your400name.  If this fails let us know the exact error and
we'll
go
> from there.  Oh, to end the telnet session they can use SIGNOFF ENDCNN
> (*YES).  There is an attention key option but this is my preferred
method.
>
> I don't know how telnetting to a S/390 looks - you know, the pf keys
and
> whatnot.  But if you telnet from a 400 to a 400 you will notice ZERO
> function difference.  However if you use DOS to telnet to a 400 you
may
> slice your wrists.
>
> Wait, here's something sexy.  I was reading all the possible
parameters on
> the TELNET command on the 400 and they include:
> Outgoing 3270 mapping table
>   Library  . . . . . . . .
> Incoming 3270 mapping table
>   Library  . . . . . . . .
>
> So I am sure uncle IBM has already come up with the best possible
mapping
> based on your 5250 keyboard du jour.
>
> Keep the faith!
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>                     "Adam Lang"
>                     <aalang@rutgersinsu       To:
<midrange-l@midrange.com>
>                     rance.com>                cc:
>                     Sent by:                  Fax to:
>                     midrange-l-admin@mi       Subject:     3270
emulation
and TCP/IP and Terminals
>                     drange.com
>
>
>                     12/18/2001 01:56 PM
>                     Please respond to
>                     midrange-l
>
>
>
>
>
>
> Hello,
>
> I am new to this list.  I do some work with an AS/400, but I am mostly
> Linux
> and PC based.
>
> I checked through your archives first and did not seem to find
anything to
> help me.
>
> I am in the process of redesigning our companies WAN structure.
Currently
> we have an AS/400 in NJ and an OS/390 in KY.  There is an SNA line
between
> the two of them.  Users that are connected to the AS/400 use
streml3270 to
> passthru to the OS/390.
>
> I have gotten our KY office to setup TCP/IP on the OS/390.  We are
> installing a TCP/IP data line between offices and eliminating the SNA
line.
> This is fine for the PCs using CA express, I figure I will just make a
> second session that points to the OS/390.  What can I do about the
dumb
> terminals?  Is there still away to use streml3270 or something like it
so
> non TCP/IP connected devices can still passthru the AS/400 to the
OS/390?
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> http://www.rutgersinsurance.com
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.