Glenn Cole wrote:

> In glancing quickly at the list (I'm on lunch break from another
> class), I notice only one thing missing:  the ability to specify a
> "default shell" for a user.

Glenn is quite correct, I intended to elaborate in the section on
login enhancements.  The debatable topic he mentioned was whether
or not logon UDCs would be executed by alternate shells. The first
pass says yes, they will.  The second pass makes it a login option.
In any case it only affects session logins, not jobs, ftp sessions,
or other similar events.

The first pass involves a TELESUP utility to plug in a default shell
for a group of users, but as he mentioned, you must still alter or
remove any login UDCs those users may have had active since invoking
an application from a login UDC in the "new" method still leaves a
dormant CI process.  As Tony Furnivall pointed out, the first pass
is not unlike a :BYE that specifies a program, parm, and info to be
executed after the :BYE is executed.  The second stage can bypass
the UDC tree altogether, however.

Jeff Kell <[log in to unmask]>  "still stuck in Sunnyvale"