After posting this original message:

I have two systems that run very well, and are pretty speedy, except for the
logon process, which for some reason is a real bear. After putting in MPE
passwords, it takes what seems like forever (usually about 4 minutes) for
Security 3000 to ask for its password. After typing in the Security 3000
password, everything is speedy again.  Can this be caused by a huge, never
been cleaned out, list of users ?

I received several replies of things to try, most of them dealing with the
$NO-HOST-CHECK put into the SECURCON.DATA.VESOFT file, others dealing with
telnet connectivity instead of NSVT, and one suggesting there might be a
pause in the logon UDC's somewhere.  I have tested all these suggestions
out, and still have the problem, but have learned some new things:

1)  I have definitely narrowed it down to specifically the logon program in
VESOFT - that is where the major holdup is
2)  Interestingly enough, when I sign on as system manager and RUN
LOGON.PUB.VESOFT,LISTUSER it takes as much as 5 minutes to get the prompt !
There are only about 20 entries total listed (on the test machine side).
3)  Running GOD takes forever too !
4)  Both test and production machine act the same way !
5)  Both test and production machines are otherwise very speedy except for
the above
6)  Most of the files have not been modified in the VESOFT account for 9
years +
7)  Getting into glance in one window, and starting a logon in another
window, shows little CPU usage (< 3%) during the entire logon process

This leads me to think that there may be some sort of file that Security
3000 keeps all this information, and that it is tremendously messy.

Wyell Grunwald

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