That same issue, logon time performance, is sometimes a thorn for companies
that require folks to log off at lunch break, and/or who run more than 1
shift.

> -----Original Message-----
> From: John Clogg [SMTP:[log in to unmask]]
> Sent: Thursday, June 14, 2001 1:58 PM
> To:   [log in to unmask]
> Subject:      Re: UDC vs Command files
>
> Donna, as usual gives an excellent answer...
>
> > for the up-shifting challenged amongst us
>
> Who might that be?
>
> Anyway, I want to add one point.  One of the supposedly "bad" things about
> UDCs is the overhead at logon time required to catalog all the UDCs
> available to the user.  These days I doubt that is a significant issue for
> most shops, but for one with a not-too-fast server and users who log on
> and
> off frequently, it could be of interest.  For instance, I have been in
> environments where several hundred users all log on at the same time (8:00
> AM - the start of a shift), and logon processing is a serious performance
> issue.  Of course, if you have a command that is used quite often, it
> could
> be worthwhile to incur the overhead at logon time, rather than searching
> through all the directories in HPPATH each time it's invoked.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *