Re: Connecting to the OS/390 via TCP/IP .... again

Yes, I could technically telnet to the mainframe from the PCs.  The problem
is that keyboard mappings and such don't translate properly with a standard
telnet.  All TCP/IP 5250/3270 emulation applications are just glorified
telnet windows.

Telnet to an AS/400 using the windows telent client.  You'll see what I
mean.

CAE does not emulate 3270, so it won't conenct directly and buying another
client piece for everyone is out of the question.

I wonder why IBM doesn't make something like CAE for the mainframe.  The
closest the have is Host On Demand it seems.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: <kmskeele@mail.volusia.k12.fl.us>
To: <midrange-l@midrange.com>
Sent: Thursday, March 21, 2002 3:10 PM
Subject: RE: Connecting to the OS/390 via TCP/IP .... again


> If the PCs can emulate 3270 then they could open multiple
sessions(windows)
> for different apps on the 390. I think that would be a better route than
> having the overhead of going through the 400.
> If the 390 can accept telnet sessions through the 400 then it could accept
> them straight from the client.
>
> -----Original Message-----
> From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> Sent: Thursday, March 21, 2002 2:52 PM
> To: midrange-l@midrange.com
> Subject: Re: Connecting to the OS/390 via TCP/IP .... again
>
>
> MVS I assume.
>
> Some PCs using CAE and some dumb terminals.
>
> I have 2 people testing the as/400 telnet to the os/390 and it works
> wonderfully.
>
> I think I will leave it at that and if any chance someone needs to access
> multiple applications, we can purchase a fat client for them.
>
> What do you mean about creating a window?
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> http://www.rutgersinsurance.com
> ----- Original Message -----
> From: <kmskeele@mail.volusia.k12.fl.us>
> To: <midrange-l@midrange.com>
> Sent: Thursday, March 21, 2002 2:38 PM
> Subject: RE: Connecting to the OS/390 via TCP/IP .... again
>
>
> >
> >
> > Yes VTAM, but is it under VM or just on OS/390(MVS) ?
> > Also are these users on 5250(dumb) terminals or PCs with emulation ?
> > If emulating on a PC you could just create a window for each app
emulating
> > 3270.
> >
> > -----Original Message-----
> > From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> > Sent: Thursday, March 21, 2002 2:28 PM
> > To: midrange-l@midrange.com
> > Subject: Re: Connecting to the OS/390 via TCP/IP .... again
> >
> >
> > VTAM
> >
> > we were connecting via streml over an SNA connection.
> >
> > Adam Lang
> > Systems Engineer
> > Rutgers Casualty Insurance Company
> > http://www.rutgersinsurance.com
> > ----- Original Message -----
> > From: <kmskeele@mail.volusia.k12.fl.us>
> > To: <midrange-l@midrange.com>
> > Sent: Thursday, March 21, 2002 2:09 PM
> > Subject: RE: Connecting to the OS/390 via TCP/IP .... again
> >
> >
> > > Adam, I had another thought....
> > > Are they running VM,VM-VTAM, and VM-TCP on the 390 ? There would be
many
> > > solutions there also.
> >
> >
> >
> > _______________________________________________
> > 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 email and any files transmitted with it are confidential and
> > intended solely for the use of the individual or entity to whom they
> > are addressed. If you have received this email in error please notify
> > the system manager.
> > **********************************************************************
> >
> > _______________________________________________
> > 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.
>
>