Job-Reset gets stuck

[Tethis]

Hello,
we have a problem with resetting a Job. We use a Sceduling-System to run a Cmd. In this Cmd we first start a reset for a Sequence:

call %ASCPATH%dsjob -server %GVServer% -run -mode RESET -wait -userstatus %P2% %P3%

and after that we start that Sequence:

call %ASCPATH%dsjob -server %GVServer% -run -mode NORMAL -param QUELL_DB=%P4% -param ZIEL_DB=%P5% -param PLANDATUM=%P6% -userstatus %P2% %P3%

The Problem occurs after the Reset-Call. The dsjob.exe starts, but isn't doing anything. We can see that the process is running, but there are no entrys in the Director.

We use this Scheme for all our productive Jobs (Sequences), but only one has this problem. We already built this Sequence totally new. What can be the reason for this problem?

[ray.wurlod]

Welcome aboard.

I presume "call " is something within your scheduler.

How long are you waiting? How long do you have to wait if resetting manually using Director? Are you attempting to reset a job that is already in a runnable stage?

Instead of using -wait in the reset run, try using -jobstatus, and tell us whether that makes any difference.

[chulett]

I've also found a need to put a short sleep - 5 seconds? - between the job reset and the job run, in spite of the -wait option. Perhaps that might help here as well.

[Tethis]

Thank you first for the fast response!

I think this problem occurs not because of the waiting time. We start the Reset with a command out of a cmd. In our Logs we can see, that the dsjob.exe for the Reset has been started. Also we can see the running dsjob.exe on the server. But the dsjob.exe isn't doing anything and does not come to an end.

Is it possible, that "hanging" dsjob.exe (which haven't come to an end correctly) from other(!) jobs hold locks, so that the reset couldn't work correctly?

[Tethis]

Hello again,

we still have the same problem from time to time. Can anybody help me out here?

Thank you a lot!