Thanks for the responses, people. Fortunately, we've been implementing 
centralized management slowly, and as a byproduct of that, the administrative 
schedules have all been updated recently by current staff members. The rest of 
the issues, like scripts outside of TSM that query TSM, have been anticipated 
and dealt with. 

Nick


On Jul 8, 2010, at 8:58 AM, Prather, Wanda wrote:

> I think if you remove the admin that defined an admin schedule, the schedule 
> fails.
> When the admin schedule runs, note it says the defining admin "issues" the 
> command:
> 
>   ANR2750I Starting scheduled command DAILYCHECKIN ( run
>    checkin ). (SESSION: 31664)
>   ANR2017I Administrator XXXXXX issued command: RUN checkin
>     (SESSION: 31664)
> 
> Also things like Autovault, other 3rd party tools, and TOR may connect to the 
> TSM server via an admin id.
> I've got perl scripts that do queries using an admin id.
> 
> But think if you query the activity log for the last xxxxx days for the admin 
> id and don't find it, you're good.
> 
> W