This is the error message I'm getting.
"ANS0299E Scheduler cannot be started manually because the value of MANAGEDSERVICES option is SCHEDULE".
I've searched the forums, and the IBM site and neither shed any light on the issue I'm having. (Also I'm not trying to manually start the client scheduler service to cause this).
The dsm.opt file is configured as:
MANAGEDSERVICES SCHEDULE WEBCLIENT
The dsmcad TSM Client Acceptor service is set to automatic, whilst the TSM schedule service is set to manual. We never try and set the TSM schedule service on the client to automatic or start it, as the schedule is controlled from the TSM server - which has succeeded in the past.
We're at a loss while all of sudden it is not working. We can ping the TSM server from the client, and when we do a "QUERY SESSION" from the dsmc command line on the client we get a return of:
tsm> query session
Session established with server ABCD5678_SERVER1: Windows
Server Version 5, Release 5, Level 1.0
Server date/time: 07/21/2009 17:38:27 Last access: 07/21/2009 16:56:26
TSM Server Connection Information
Server Name.............: ABCD5678_SERVER1
Server Type.............: Windows
Archive Retain Protect..: "No"
Server Version..........: Ver. 5, Rel. 5, Lev. 1.0
Last Access Date........: 07/21/2009 16:56:26
Delete Backup Files.....: "No"
Delete Archive Files....: "Yes"
Node Name...............: ABCD1234
User Name...............:
If I could provide any further information I'd be glad to. Thanks if anyone can help.
"ANS0299E Scheduler cannot be started manually because the value of MANAGEDSERVICES option is SCHEDULE".
I've searched the forums, and the IBM site and neither shed any light on the issue I'm having. (Also I'm not trying to manually start the client scheduler service to cause this).
The dsm.opt file is configured as:
MANAGEDSERVICES SCHEDULE WEBCLIENT
The dsmcad TSM Client Acceptor service is set to automatic, whilst the TSM schedule service is set to manual. We never try and set the TSM schedule service on the client to automatic or start it, as the schedule is controlled from the TSM server - which has succeeded in the past.
We're at a loss while all of sudden it is not working. We can ping the TSM server from the client, and when we do a "QUERY SESSION" from the dsmc command line on the client we get a return of:
tsm> query session
Session established with server ABCD5678_SERVER1: Windows
Server Version 5, Release 5, Level 1.0
Server date/time: 07/21/2009 17:38:27 Last access: 07/21/2009 16:56:26
TSM Server Connection Information
Server Name.............: ABCD5678_SERVER1
Server Type.............: Windows
Archive Retain Protect..: "No"
Server Version..........: Ver. 5, Rel. 5, Lev. 1.0
Last Access Date........: 07/21/2009 16:56:26
Delete Backup Files.....: "No"
Delete Archive Files....: "Yes"
Node Name...............: ABCD1234
User Name...............:
If I could provide any further information I'd be glad to. Thanks if anyone can help.