Command Schedule on NT
1998-06-30 02:51:15
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
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Command Schedule on NT,
Michael Garnebode <=
|
|
|