Michael,

What you are seeing with the ANR0482W message is your IDLETIMEOUT
period expiring, not your schedule window elapsing.

I saw this when we first began using the PRESCHEDULECMD as well.

From your description, I'm not sure if it is the command.cmd file
or the ADSM scheduler which is responsible for starting your
incremental backup.

If it is the former, your schedule session will time out while
the session initiated by your command.cmd script will remain
active until the backup has finished.

If, however, it is the latter, there may be something wrong with
the exit status of your script. When using PRESCHEDULECMD, ADSM
will wait until the script exits before it proceeds with the
backup. If it does not receive the exit status from the script, I
don't believe it will proceed with the backup. Using the
PRENSCHEDULECMD would solve this problem, as it instructs the
scheduler not to wait for the script to exit. In your case,
however, it doesn't sound like that's what you would want if the
services are meant to be stopped prior to running the backup.

 -- Tom

On Tue, 30 Jun 1998, Michael Garnebode wrote:

>Hi ADSM'ers,
>i have following situation on some WinNT Clients (v3.1.0.3).
>I have write a command.cmd file to stop some services on nt
>after that we start a incrementall backup. When the backup
>finish we start the services.
>This script will start with the ADSM-Scheduler Service with
>a startup window of 15 miniutes.
>The scheduler start the script. After 15 minutes i see in the
>activity log the message
>Start
>06/29/1998 20:30:01  ANR2561I Schedule prompter contacting NTMDC0010103
>                      (session 603) to start a scheduled operation.
>06/29/1998 20:30:02  ANR0406I Session 604 started for node NTMDC0010103
>(WinNT)
>                      (Tcp/Ip 213.1.113.218(3123)).
>END
>06/29/1998 20:45:58  ANR0482W Session 657 for node NTMDC0010103 (WinNT)
>                      terminated - idle for more than 15 minutes.
>
>But the script is already started and have already done. I see it in the
>backup-protocol.
>One Solution is to update the startup window to 1 hour.
>
>My question is: must the script finish in the 15 minutes start up
>windows ?
>                When the schedule command not finished in the startup
>window where is
>                the return code for the scheduler that he says i have
>already started the
>                command ?
>
>regards
>michael
>