Hopefully someone on this list can help me with this problem.  I have a user
who backs ups several W2k machines.  Six of these machines are having a
problems with numerous ports taken up by the TSM scheduler.  All of the ports
point to the same PID and all are executing dsmcsvc.exe.  The system I'm
looking at right now has 19 ports used for the dsmcsvc process (all having the
same process id).

Does anyone know how this could happen?  Some of the clients having the problem
are running the 4.1.2.0 client and some are running 4.2.1.26 client.  The
server is an AIX 4.3 box running the 4.1.2 server.  Checking the dsmerror.log
on the client machine, I see several of these types of messages:


03/25/2002 14:17:01 ConsoleEventHandler(): Caught Ctrl-C console event .
03/25/2002 14:17:01 ConsoleEventHandler(): Cleaning up and terminating
Process ...
03/25/2002 14:17:10 cuSignOnResp: Server rejected session; result code: 53
03/25/2002 14:17:10 sessOpen: Error 53 receiving SignOnResp verb from server
03/25/2002 14:17:10 ANS1353E Session rejected: Unknown or incorrect ID entered

and


3/26/2002 15:06:12 ConsoleEventHandler(): Caught Logoff console event .
03/26/2002 15:06:12 ConsoleEventHandler(): Process Detached.
03/26/2002 15:06:16 ConsoleEventHandler(): Caught Logoff console event .
03/26/2002 15:06:16 ConsoleEventHandler(): Process Detached.
03/28/2002 17:18:58 ConsoleEventHandler(): Caught Logoff console event .


Could these be causing the scheduler to use additional ports in any way?  I
don't see any other obvious errors in the dsmsched.log or dsmerror.log.

Any help would be appreciated.

Diana