DB2 Admin performance issue resolved.

[Patrick Finnegan]

Running Versions 7.X and *.X on Windows 2000.

We experienced very slow response times for some admin functions
executed via the command line and the GUI. for example "db2 list
tablespaces" was taking over a minute to return a list of 100
tablespaces. Noticed that delays only occurred if the auth log-on was
an NT domain ID in a local group(using DB2_GRP_LOOKUP=LOCAL).
Response times were fine for locally defined auth ids. I checked the
security access log in the event viewer on the DB2 server and noticed
that there were a large number of entries for DB2 instance service
local log-on id. I ran several DB2 administration commands on the DB2
server and these generated a massive number of security authentication
entries in the log. I modified the DB2 services to run under the
default NT "LocalSystem" account and restarted. Responses to command
line administration commands and GUI are now much faster and there are
no security entries in the log corresponding to DB2 commands.

It may be the authentication mechanism on the local SAM database on
the DB2 server is poor or DB2 is trying to authenticate the local
service userid at the PDC first and then locally. At any rate running
DB2 services under the local system account seems to improve all round
performance.

NB: The only caveat is that services which run under the LocalSystem
account cannot see UNC drives.