Is it "will not function" or is it more like "hasn't functioned yet"?

When running in polling mode, the immediate action is not necessarily
immediate; it would be picked up the next time the client polls the server
for its next scheduled event, which is based on the QUERYSCHEDPERIOD
client setting.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Karel Bos <Karel.Bos AT NUON DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/13/2002 08:54
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        schedmode polling and immediate client actions



Hi,

We have changed our scheduling mode from prompted to polling. Scheduled
back-ups run fine. The immediate client schedule won't run. The status of
the immediate schedule turns to pending and will not function.


Schedule Name @621
Description -
Action INCREMENTAL
Options -
Objects -
Priority 1
Start date 2002-03-13
Start time 16:32:17
Duration 1
Duration units DAYS
Period -
Period units ONETIME
Day of Week ANY
Expiration -


         Node Name: X
   Scheduled Start: 03/13/02 16:32:17
      Actual Start:
         Completed:
            Status: Pending
            Result: