According TSM Admin manual, it says that if the scheduling mode is set to
prompted, the client processes the command immediately.
If the scheduling mode is set to polling the processes the command at its
prescribed time interval.  Looks like the prescribed time interval maybe
referring to the client's polling interval which in this case is 12 hours.

If you want to try to kick it off immediately change the schedule mode to
prompted, or change the polling interval to less than 12 hours.
All of my clients are in prompted mode, and never had any problem kicking
off an immediate client action.   If you do change the schedule mode, the
schedule needs to be recycled.

Sung Y. Lee
Office  (512) 823-1012



                    Gerald
                    Wichmann             To:     ADSM-L AT VM.MARIST DOT EDU
                    <gwichmann@SAN       cc:
                    SIA.COM>             Subject:     Client Actions
                    Sent by:
                    "ADSM: Dist
                    Stor Manager"
                    <ADSM-L AT VM DOT MAR
                    IST.EDU>


                    12/04/2001
                    03:08 PM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"





I just defined a client action on the server to run a command.. I then
restarted the scheduler (windows platform). It didn't run so I looked on
the client's dsmsched.log file to see what it was doing and found this:

12/04/2001 11:41:54 --- SCHEDULEREC QUERY BEGIN
12/04/2001 11:41:54 --- SCHEDULEREC QUERY END
12/04/2001 11:41:54 Next operation scheduled:
12/04/2001 11:41:54
------------------------------------------------------------
12/04/2001 11:41:54 Schedule Name:         @11
12/04/2001 11:41:54 Schedule Name:         @11
12/04/2001 11:41:54 Action:                Command
12/04/2001 11:41:54 Objects:               "c:\Program
Files\Tivoli\TSM\TDPSql\sqldiff.cmd"
12/04/2001 11:41:54 Options:
12/04/2001 11:41:54 Server Window Start:   11:17:01 on 12/04/2001
12/04/2001 11:41:54
------------------------------------------------------------
12/04/2001 11:41:54 Command will be executed in 11 hours and 33 minutes.
12/04/2001 11:41:54 Command will be executed in 11 hours and 33 minutes.
12/04/2001 12:20:24 Querying server for next scheduled event.


Now the client is set to polling and only poll's every 12 hours. But I
was a bit surprised, to say the least, that it wasn't going to run my
client action for 11 hours and 33 minutes. Why doesn't it run the
command immediately? This is kind of annoying.. Is there some logic
behind this behavior?

Gerald Wichmann
System Engineer
StorageLink
408-844-8893 (v)
408-844-9801 (f)