and he can route this simple command through... it's not just a single
machine then!!

god bless us! :)


yu chen








From: O1=INET00/C=US/A=IBMX400/P=STATEFARM/DD.RFC-822=ADSM-L\@VM.MARIST.EDU
on 01/28/99 09:47:44 AM
To:   ADSM-L
cc:
Subject:  Re: Authority Questions...

     Ohhhhh it gets sooooooo goooood

     stuff like... OK, I won't point out the extent of the actions an adsm
     admin could perform...

     Just as with HSM under MVS, ADSM admins have the ability to perform
     more alterations WITHOUT root or console authority across more systems
     than any single root or console user.

     *** neat twist with the scheduler the other day ***
     OK, not easily can you have two schedulers running on the same client
     dealing with two different adsm servers
     BUT YOU CAN have the one adsm server schedule a command of
     dsmc incr /somefilesys -serv=someotherserver -pass=clientpass
     so a scheduled event from adsmserver1 could force an incremental (or
     partial incremental, only selected file systems) to adsmserver2

     later,
           Dwight


______________________________ Reply Separator ____________________________
_____
Subject: Re: Authority Questions...
Author:  Thomas.Denier (Thomas.Denier AT MAIL.TJU DOT EDU) at unix,mime
Date:    1/28/99 9:10 AM


Central scheduling adds an interesting twist to this discussion. Using the
DEFINE SCHEDULE or DEFINE CLIENTACTION command with ACTION=COMMAND allows
an
ADSM server administrator to run arbitrary commands on any clients using
central scheduling. These commands will run with whatever privilege level
the
scheduler process has. This is normally root in Unix environments. I gather
that it is normally a highly privileged ID on other types of client
systems.