This is a win2k system and I have seen this on some others we have too.
Those are at level 5.1.5.2 and 5.1.1.3. This one is 5.1.5.2.
Nodename is in upper case in the options file, the service has been removed
and re-created more than once but still have the error message.
The output below is correct

Connecting to service 'tsm central scheduler service' ...

Service Configuration/Status:

Service Name   : tsm central scheduler service
Logon Account  : LocalSystem
Start Type     : Auto
Current Status : Started

TSM Client Service Registry Settings:

Client Service Type = Client Scheduler Service
Client Directory    = "c:\Program Files\Tivoli\TSM\baclient\dsmcsvc.exe"
Options file        = c:\Program Files\Tivoli\TSM\baclient\dsm.opt
Event Logging       = YES
TSM Client Node     = CP-ITS-SQLQA-2
Comm Protocol       = (value not currently set)
Server              = (value not currently set)
Server Port         = (value not currently set)
Schedule Log        = C:\Logs\dsmsched.log
Error Log           = C:\Logs\dsmerror.log
MSCS Enabled Node   = (value not currently set)
Cluster name        = (value not currently set)

C:\Program Files\Tivoli\TSM\baclient>

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   gillg AT saic DOT com
Phone:  (858) 826-4062
Pager:   (877) 905-7154


> -----Original Message-----
> From: Bill Boyer [mailto:bill.boyer AT VERIZON DOT NET]
> Sent: Wednesday, November 13, 2002 12:30 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Error initializing TSM Api
>
> I believe he's on NT and the password is in the registry, not in a file as
> some OS's. I'm not even sure if you remove the TSM service(s) if that will
> remove the registry keys. But removing and then re-installing the
service(s)
> will at least correct the password in the registry.
>
> I have seen a problem if you were not specifying a NODENAME in the DSM.OPT
> file and the value assigned to the %COMPUTERNAME% env variable was
> lower-case. How it gets assigned as lower-case, I'll never know, but the
> encrytpion algorithm TSM uses to store the password in the registry looks
> like it didn't UPPER(NODENAME) first in some cases. So the scheduler would
> work until you ran the line command which would ask you to re-entry the
> password. Then the scheduler wouldn't work anymore. Also affected the CAD
> service.
>
> Bill Boyer
> DSS, Inc.