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

What ip address are you defining?

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: Wednesday, March 20, 2002 10:00 AM
Subject: RE: Connecting to the OS/390 via TCP/IP .... again


> I have not worked on OS/390 but on VSE the TCP stack could be configured
to
> allow a telnet session to come into a TCP menu. This would allow the
telnet
> user to access different apps
> (prodcics, roscoe, etc.) Have them check into that.
> DEF TEL,ID=T156001,TERM=WTCPW001,TAR=TCPMENU,IP=10.1.156.1,POOL=YES
> This is my example of defining a ip address to a VTAM name and and
> application target TCPMENU
> They would have to code the menu as an app itself (and create the menu)
> A session manager is a solution also, but there are ways around it.
> -----Original Message-----
> From: Adam Lang [mailto:aalang@rutgersinsurance.com]
> Sent: Wednesday, March 20, 2002 9:36 AM
> To: midrange-l@midrange.com
> Subject: Connecting to the OS/390 via TCP/IP .... again
>
>
> Ok, from what I have tried out it seems the AS/400 telnet client is the
way
> to go.
>
> One issue I have come across.  The OS/390 has a couple apps: PRODCICS,
> Roscoe, etc.  Well, from what the Mainframe guy in the remote office told
> me, is that they can only specify one application.  And if the user wants
to
> go to another one, they can't, because the telnet session automatically
> sends them to the one default app.
>
> He says to get around that we need a Session Manager program.  About $5500
a
> year.
>
> Does this make sense?  Is there a better/cheaper way?
>
> 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 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.
>
>