Mehdi,
>From the client side, are there any entries in the dsmsched and dsmerror
log files from stopping and restarting the TSM Central Scheduler
service? You could update/delete then redefine the TSM Central Scheduler
from the GUI then check the dsmsched and dsmerror log files.
>>>Another issue that I cannot explain is that if I stop the "TSM Client
scheduler" windows service and run "dsmc schedule"
it will not be started, but schedule works fine!<<<
Strange, check if you associated the current nodename to more than one
TSM schedule.
BERTAUT TCHUISE
TSM/NetApp Storage Administrator
Legg Mason Technology Services
*410-580-7032
BTchuise AT leggmason DOT com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Mehdi Salehi
Sent: Thursday, December 03, 2009 5:10 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] schedule problem
Hi,
In TSM ba client 6.1 for Windows, I have enabled TSM Client scheduler
via TSM GUI. In windows services I can see the service as "Started".
However associated schedule in TSM server does not start for this
client.
Interestingly when I run "dsmc schedule" from command line in the
windows box, schedule works as expected. Another issue that I cannot
explain is that if I stop the "TSM Client scheduler" windows service and
run "dsmc schedule"
it will not be started, but schedule works fine! Seems that TSM Client
scheduler and what "dsmc schedule" bring up are two different things!
Thanks
IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security numbers,
account numbers, or personal identification numbers. Delivery, and or timely
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends
that you do not send time sensitive
or action-oriented messages to us via electronic mail.
This message is intended for the addressee only and may contain privileged or
confidential information. Unless you are the intended recipient, you may not
use, copy or disclose to anyone any information contained in this message. If
you have received this message in error, please notify the author by replying
to this message and then kindly delete the message. Thank you.
|
