Several things come to mind.  

1) Have a look a the SECDUMP and SECLOAD commands - allows you to unload
and reload Security/3000's config files.  We used to use these commands
to transfer the user and password information from our live system to
our DR server. 
2) shutdown and re-start the mpex hello trap (we no longer have any
hp3000s on site, but can remember an odd situation where the logon
process for qedit for windows would very occasionally stall for a few
minutes. The resolution was simply to stop/start the mpex trap).  
3) Are there any VESOFT logfiles lurking that you could delete ?  
4) Is it possible that the LOGON,LISTUSER is trying to access a remote
server (e.g a logfile server ?) and is waiting for that remote server to
respond ? 
5) Does glance tell you what the LISTUSER process is doing - e.g. look
at files it's accessing and/or see what resource the process is wait for
!

Best of luck 

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Wyell Grunwald
Sent: 06 January 2010 14:29
To: [log in to unmask]
Subject: [HP3000-L] Update on Security 3000 slowness problem

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 *

The contents of this email are confidential to the intended recipient and may not be disclosed. Although it is believed that this email and any attachments are virus free, it is the responsibility of the recipient to confirm this.

Details of Smith & Williamson group companies and Nexia Smith & Williamson Audit Limited and their regulators (where applicable), can be found at this URL

http://www.smith.williamson.co.uk/disclosure

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