CODEWITHSUNDEEP
cmdautosys
Francis Ducharme
Francis Ducharme

Reputation: 4987

Jobs always stay in STARTING status

I'm pretty new to AutoSys (version 4.5 here) and I've got this problem where the jobs I create always stay in "STARTING" status after execution.

Here's the command, pretty straightforward:

DEL /F /Q \\server\share\*.*
IF NOT ERRORLEVEL 0 GOTO EndError
EXIT 0
:EndError
EXIT %ERRORLEVEL%

At first I did not have the EXIT statements, so I thought that was it. But alas, it's still doing it. Mind you, I'm FORCE STARTING this specific job to test it. It is part of a box, but I'm not starting the box itself, I want to test the jobs piece by piece.

Any ideas ?

Upvotes: 0

Views: 4179

Answers (2)

renaissanceMan
renaissanceMan

Reputation: 433

I don't think this is an answer for the question above but if your you "Start"ed your job and it says [STARTJOB] and just sits there, this may be what is happening. If you "Start" a job that has a condition all that will happen is the job will sit there until the autosys condition is met, it won't actually run. You may be starting other jobs that don't have a Condition and they will Start and run when you "Start" them. "Force Start" the job and it will run.

Upvotes: 0

Vamsi Rama Krishnam Raju
Vamsi Rama Krishnam Raju

Reputation: 46

job cannot connect to the AutoSys service on a machine where job should be started. Restart or configure service (agent).

Upvotes: 2

Related Questions