Trevor,

I see what you want, and I can agree that would be beneficial.  Why not take it
a step further?  When you delete an  ADMIN ID, all of the schedules that were
assigned to the deleted ADMIN ID are reassigned to the deleting ADMIN ID.  If
ADMINA takes over for ADMINB, have ADMINA delete ADMINB, and all of the
schedules change over at that time.

Nick Cassimatis
nickpc AT us.ibm DOT com

If you don't have the time to do it right the first time, where will you find
the time to do it again?

Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Re[2]: Admin deleted, job not run


Hi,

Time for my 2 cents worth.

I have no problem with schedules being associated with administrators,
and those schedules not being able to run if the administator is
deleted. However, I do have a problem with not being told that something
I am about to do ie delete an administator, is going to have an adverse
affect on my ADSM server. And I think that is is unreasonable to have to
remember to check for these sorts of things. We have a few dozen
administrators with enough privilege to add/update schedule (mostly
within a single domain) and maybe 100 scheduled events.

What I'd like to see is that when a 'remove admin' is performed, a check
should be made that there are no schedules associated with that
administator. I see it working along the lines of a 'remove node' where
a check is made that there is no data stored against that node.


Trevor