ADSM-L

Re: WinNT & running of batch processes

1998-09-10 09:21:50
Subject: Re: WinNT & running of batch processes
From: Christo Heuer <christoh AT ABSA.CO DOT ZA>
Date: Thu, 10 Sep 1998 15:21:50 +0200
Hi Pete,

It turned out to be the level of code that we had on this box.
We have the latest level and it is working now - thanks
again for the reply.

Regards
Christo Heuer



>I assume that you are running the scheduler as a service.
>
>Services running under the local system account (the default for the ADSM
>scheduler) have no environment and therefore no defined
>search path exists, so you should either fully qualify the name of the
batch
>file in your scheduled command or place the batch file in the NT
>system32 directory.
>
>You could also have the service log in as a non-system account which
includes
>the directory containing the batch file in it's search path.
>
>If the scheduled command runs when the scheduler is running interactively
(as
>opposed to running as a service) it's likely that
>the service isn't finding that batch file as described above.
>
>Hope this helps .....
>
>Pete Tanenhaus
>ADSM NT Client Development


---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 09/09/98
12:08 PM ---------------------------
12:08 PM ---------------------------


ADSM-L AT VM.MARIST DOT EDU on 09/09/98 08:35:44 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: WinNT & running of batch processes


Christo,

>
>I've tried it as a .bat and as a .cmd - but it still does not kick off?
>The scheduler runs, kicks off and immediately comes back saying
>that the command will be retried in 20 minutes. It's almost as if at can
>not connect to the ADSM server at that moment. No error messages
>in the dsmsched.log or the dsmerror.log!
>
>All it says in the dsmsched.log is
>executing scheduled command now!
>command will be retried in 20 minutes.
>

What level of the ADSM client scheduler are you using?  There were some
problems with
running COMMAND type schedules in the initial V3 levels of the client
scheduler
which
may be causing your problem.  If you are not at a recent level of the V3
client, getting the latest
PTF from the FTP site and reinstalling the scheduler service may solve your
problem.


Chris Zaremba
ADSM Agent Development
internet  zaremba AT us.ibm DOT com



=
<Prev in Thread] Current Thread [Next in Thread>