Tim This is your problem:
> Cad Schedule Service = TSM I can't tell you how or why this has changed, but to resolve it you need to update the properties of the client acceptor service to tell it the real name of the scheduler service, and then restart the client acceptor. DSMCUTIL UPDATE CAD /NAME:"TSM Client Acceptor" /CADSchedName:"TSM Scheduler" DSMCUTIL STOP /NAME:"TSM Client Acceptor" DSMCUTIL START /NAME:TSM Client Acceptor" Regards Neil Timothy Hughes <[email protected]> 23/11/2009 13:25 Message Size: 6.4Kb To [email protected], "ADSM: Dist Stor Manager" <[email protected]> cc Subject Re: The service 'TSM' does not exist ?? Neil, Thanks! Here is the output D:\Program Files\Tivoli\TSM\baclient>dsmcutil query cad /name:"TSM Client Acceptor" TSM Windows NT Client Service Configuration Utility Command Line Interface - Version 6, Release 1, Level 0.2 (C) Copyright IBM Corporation, 1990, 2009, All Rights Reserved. Last Updated Jul 5 2009 TSM Api Version 6.1.0 Command: Query TSM Client Service Parameters Machine: SNI287(Local Machine) Connecting to service 'TSM Client Acceptor' ... Service Configuration/Status: Service Name : TSM Client Acceptor Image Path : "D:\Program Files\Tivoli\TSM\baclient\dsmcad.exe" Logon Account : LocalSystem Start Type : Auto Current Status : Started TSM Client Service Registry Settings: Client Service Type = Client Acceptor Service Partner Service = TSM Remote Client Agent Cad Schedule Service = TSM HTTP Port = 1581 Secure HTTP Port = (value not currently set) Web Ports = (value not currently set) Options file = D:\Program Files\Tivoli\TSM\baclient\dsm.opt TSM Client Node = SNI287 D:\Program Files\Tivoli\TSM\baclient> DSM.opf file NODENAME SNI287 tcpclientaddress xxx.xx.xx PASSWORDACCESS GENERATE TCPSERVERADDRESS xxx.xx.xx VMCHOST xx.xx.xxx.xx VMCUSER vcbuser VMCPW vcbu$er VMLIST SNI08,SNI09,SNI110 SUBFILEBACKUP YES SUBFILECACHEPATH d:\tsmsubfile SUBFILECAcHESIZE 100 commmethod tcpip MANAGEDSERVICES WEBCLIENT SCHEDULE DOMAIN ALL-LOCAL VMBACKUPTYPE FILE Noet: Manual Backups complete successfully Neil Schofield wrote: >Tim > >Sorry if I wasn't clear in my original response. It's the properties of the >TSM Client Acceptor service we need to determine with the DSMCUTIL QUERY >command, rather than the properties of the TSM Scheduler service. Because >the MANAGEDSERVICES entry in your DSM.OPT includes SCHEDULE, the name of >the scheduler service should be defined as a property of your TSM Client >Acceptor service. > >Can you post the output of >DSMCUTIL QUERY CAD /NAME:"TSM Client Acceptor" > >Regards >Neil > >----------------------------------------- >Find out how our new character Numptee is causing all sorts of >problems by putting the wrong things down his toilet and drains - >check out his videos and look at what you can do to help keep your >drains running free. > >Visit http://www.yorkshirewater.com/binit > >The information in this e-mail is confidential and may also be >legally privileged. The contents are intended for recipient only >and are subject to the legal notice available at >http://www.keldagroup.com/email.htm Yorkshire Water Services >Limited >Registered Office Western House Halifax Road Bradford BD6 2SZ >Registered in England and Wales No 2366682 > >
