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.
>
>