Goran,
with Exchange DB on clustered environment my strategy always has been to
keep the scheduler (that is related to the database in question)
active only on the machine the database is currently running on.

So when the database changes from one machine to another, the TSM
scheduler gets stopped on one machine and started on the target machine.
Just keep in mind that you have to make sure the TSM password for the
node always stays synced on all participating machines.

Good luck,
best regards,
Michael Bartl

Am 07.12.2006 um 10:47 schrieb goc:

hi, we are doing some heavy DB reallocation and stuff and i'm very
confused
since we are using 4 node cluster with 35 oracle databases \o/ ...
since the
DB can be active on any node i made a script which checks where it
is and
manipulates the dsmcad process accordingly ... but that was not my
question
:-)
the Q: is there a way to simply enable/disable schedule(s) rather than
removing the node (or removing the schedule from node properties) from
schedule ?

i mean something simple as checkbox like in admin schedules
"Schedule is
active" thingy ,

would that be nice or what ?

thanks
goran

TSM 5.3.4 on AIX 5.2
58.4TB of data

--
Michael H. Bartl                              Mail: mbartl AT space DOT net
SpaceNet AG                                   Tel:  089 / 32356-151
Joseph-Dollinger-Bogen 14                     Fax:  089 / 32356-299
D-80807 Muenchen                              http://www.space.net/

Genug von Viren und Spam? SpaceNet_Mail hilft Ihnen - lesen Sie, wie
SpaceNet_Mail beim Muenchner Verkehrs- und Tarifverbund erfolgreich
eingesetzt wird: http://www.space.net/mvvnews/index.html

Was wir sonst noch fuer Sie tun koennen, finden Sie unter:
http://www.space.net/