All we do is set the schedule Expiration Date to some day in the past and
when we want to reactivate it, we change it back to NEVER.

I agree having an "active/inactive" option like with Admin schedules,
would be nice/consistent.

Also, as far as scheduling flexibility is concerned, while the changes in
5.3 were handy, they are still lacking (like a time range option - e.g.
only run or don't run between 8:00 and 12:00)




goc <goran.k AT VIP DOT HR>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
12/07/2006 04:47 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
[ADSM-L] schedule manipulation :)






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