RE: Telnet Exit Point - Chicken or Egg?

["Kurt Goolsbee" <kurt.goolsbee@xxxxxxxxxxxxx>]

The Telnet Initialization Exit Point is invoked after the connection
negotiation is done.  It is invoked from one of the Telnet jobs.  One of the
uses of the exit is to assign a device name, thus it must be done before the
users job has actually started.  There is only a userid passed if the Telnet
client is set to sign on automatically.  Some useful things you can do with
this exit is to prevent connections from certain ip addresses or subnets,
preventing users from creating printer sessions, prevent users from doing
auto sign on. 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Sunday, July 25, 2004 3:14 PM
To: Midrange Mailing List
Subject: Telnet Exit Point - Chicken or Egg?

Having solved the programming issues about coding an exit point (thanks
Scott) I now have to get my head around how to use the exit point (which I
thought I understood).

I was going to use the exit point to control who could access the iSeries
using telnet but I think I am confused now.  When the device is initialized,
the exit point is invoked, so, how I can find out WHO did the invoking if
the device isn't even created yet?  One of the parameters has a User profile
field but, where would the value for this come from since the device hasn't
been created yet and therefore has no way to capture the user profile?

To restate, if the device hasn't been initialized, how can there be a user
profile passed during device initialization? Seems like a chicken or egg
thing....

I guess I need more of a Telnet logon exit point.  I want to know who tried
to log on using telnet, not just that a telnet device was initialized. Or am
I just jelly-brained from working all weekend......?

Pete Helgren
Value Added Software,Inc.
801.581.1154 x202