There are two possible client scheduling modes, polling and prompted.  Your
client is in "prompted" mode.

The server can be set to allow "polling", "prompted", or "any".  Do a "q
stat and look for this line:
    Scheduling Modes: Any
If it is set to polling, that will be why your client has missed its
schedule.

To put the client back to polling mode, go to its options file and change it
from "schedmode prompted" to "schedmode polling", and restart the daemon.

If you want to change it on the server, the command is "set schedmode any".

> -----Original Message-----
> From: Reinhold Wagner [SMTP:rwagner AT ZEUNASTAERKER DOT DE]
> Sent: Friday, December 22, 2000 6:21 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      node is missing its scheduled event but daemon is running
>
> folks,
>
> one of our *SM client nodes (TSM v4) is missing its schedule since monday.
> In
> dsmsched.log we find after _next operation scheduled:_ the following
> message:
>
> Waiting to be contacted by the server.
>
> while our v3 clients show this message:
>
> 12/21/00   14:49:26 Server Window Start:   22:20:00 on 12/21/00
> 12/21/00   14:49:26
> ------------------------------------------------------------
> 12/21/00   14:49:26 Schedule will be refreshed in 1 hour.
>
> Server is 3.1.2.40.
>
> Seems that the missing node is waiting to be triggered by the server
> instead of
> querying the schedule and start the backup by itself.
>
> Any ideas?
>
> TIA
>
> Reinhold Wagner, Zeuna Staerker GmbH & Co. KG