RE: telnet exit points

My belief is that you can achieve the functionality you want, by using a
combination of the telnet exit point and a couple of system values. The best
way I know of to find out if this will meet your own particular needs is to
just try it and experiment a little bit.

HTH

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of brian
Sent: Sunday, September 18, 2005 3:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: telnet exit points

On Sun, 18 Sep 2005, Shannon ODonnell wrote:
> I'm not following what it is you want to do.  If they don't see a sign on,
> how will you even know what user profile is attempting to sign on?

Maybe I want to drop them based on their IP, or time of day, or some other
consideration, and don't want to give them a chance to play around with my
signon screen. Looks to me like IBM overlooked something fairly major.

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of brian
> Sent: Sunday, September 18, 2005 3:06 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: telnet exit points
>
> On Sun, 18 Sep 2005, Shannon ODonnell wrote:
> > You need to read this article and try the download code first, before
you
> > jump to conclusions, because based on your comments, it appears to me
that
> > you are missing the whole point of the telnet exit program capability.
>
> "For example, a Telnet application might want to log who is signing on to
> your AS/400. You can get this information from the parameter named ETGUP.
> When the Telnet server passes control to the exit point application (your
> program), the field named ETGUP will contain the user ID of the person
> attempting to log on to your system."
>
> This tells me that the exit point program gets called AFTER the client has
> gotten the signon screen and entered his credentials.
>
> > On Sun, 18 Sep 2005, Shannon ODonnell wrote:
> > > "A Telnet Exit Program Tells You Who's Knocking At Your Door."
> > > http://www.itjungle.com/mpo/mpo091202-story06.html
> >
> > So it looks like no, there is no pre-signon ability.
> >
> > > -----Original Message-----
> > > From: midrange-l-bounces@xxxxxxxxxxxx
> > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of brian
> > > Sent: Sunday, September 18, 2005 2:29 PM
> > > To: midrange-l@xxxxxxxxxxxx
> > > Subject: telnet exit points
> > >
> > > I was just looking through WRKREGINF at the available exit points.
There
> > > seem to be only two in my release related to telnet. It's not clear to
> me
> > > whether it's possible to insert my logic before the telnet client ever
> > > gets a signon screen or not. It looks to me as if QIBM_QTG_DEVINIT is
> > > post-signon.
> > >
> > > I want to be able to hang up on people before they ever see the signon
> > > screen. Possible through exit points?
> > > --
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > 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@xxxxxxxxxxxx
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > > 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@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > 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@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > 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@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> 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@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>