I updated the schedule while logged in as "admin".  
It now has "admin" as the "Last Update by". 

   Last Update by (administrator): ADMIN

Will see what happens this evening.

If this IS how it works, that says you should ONLY create/update a admin 
schedule while logged in as an ID that will never be deleted.

btw:  this is TSM v6.3.5

Rick



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Lee, Gary
Sent: Tuesday, July 05, 2016 9:38 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ANR2174E - admin script failed

I believe that the id who last updated the administrative schedule is its owner.
Just update the sched with the same starttime for instance, and it should take 
off.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Rhodes, Richard L.
Sent: Tuesday, July 05, 2016 9:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] ANR2174E - admin script failed

Q)  Now do you set the TSM Admin ID that an administrative script runs as?


Our team lead retired last week and we deleted her TSM admin id
from all our TSM servers.  The next day, one of our tsm servers
started failing our admin script that performs the db backup
and prepare.

  ANR2174E Administrator xxxxx is not registered.
    Schedule P_ADMINPROCESSES is not processed and
    is marked as failed.

The error manual says this:

  User response: Update the command schedule with a
    valid administrator ID which has the proper authority
    to execute the scheduled command.

So I pull up the "update sched" cmd and look for some kind of parm
to set the id the script runs as.  But, I don't see one.  I see no
way to tie a schedule to a admin ID, whether when the schedule is
created or updated.  I don't see anything in a admin schedule that
specifies the ID to run as.

  ./run_cmd.ksh  -l tsmX q schedule P_ADMINPROCESSES type=admin f=d
                 Schedule Name: P_ADMINPROCESSES
                   Description: Backup DB /devconfig / volhist
                       Command: run p_adminprocesses
                      Priority: 5
               Start Date/Time: 04/19/06   19:36:00
                      Duration: 1 Hour(s)
                Schedule Style: Classic
                        Period: 1 Day(s)
                   Day of Week: Any
                         Month:
                  Day of Month:
                 Week of Month:
                    Expiration:
                       Active?: Yes
  Last Update by (administrator): xxxxxx
         Last Update Date/Time: 03/28/13   11:34:48
              Managing profile:

Other than "Last Update by", nothing specifies an admin id to run the script as.


-----------------------------------------

The information contained in this message is intended only for the personal and 
confidential use of the recipient(s) named above. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it to the 
intended recipient, you are hereby notified that you have received this 
document in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately, and delete the original message.


-----------------------------------------
The information contained in this message is intended only for the personal and 
confidential use of the recipient(s) named above. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it to the 
intended recipient, you are hereby notified that you have received this 
document in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately, and delete the original message.