Are there any other little dependencies on the creating/updating admin that
one might not be aware of?  I recently wanted to remove an admin and got a
hint that the schedules might not run, but no other warnings?

Thanks, Sheelagh
------------------------------------------------------------------------------
Sheelagh Treweek                         Email: sheelagh.treweek AT oucs.ox.ac 
DOT uk
Sheelagh Treweek                         Email: sheelagh.treweek AT oucs.ox.ac 
DOT uk
Oxford University Computing Services     Tel:   +44 (0)1865 273205
13 Banbury Road, Oxford, OX2 6NN, UK     Fax:   +44 (0)1865 273275
------------------------------------------------------------------------------
> From owner-adsm-l AT VM.MARIST DOT EDU  Tue Jul 28 16:20:29 1998
> From owner-adsm-l AT VM.MARIST DOT EDU  Tue Jul 28 16:20:29 1998
> Date: Tue, 28 Jul 1998 07:55:44 PDT
> From: Tom Brooks <tbrooks AT VNET.IBM DOT COM>
> Subject: Admin deleted, job not run
> To: ADSM-L AT VM.MARIST DOT EDU
>
>  This is working as designed. Scheduled admin commands make the same check
> on authority at run time, just the same as if an admin issued the command
> manually. Ensures at run time that the admin still has the correct authority.
> The admin used is the admin of the last admin to define/update the schedule.
>
> Tom Brooks
> ADSM Development
>