Hello
E/M 6.3.01 just stops running jobs sometimes. This happened in 6.2 and we were hoping that the upgrade would fix it ... nope.
For instance, today a cyclic job just stop running.
Selecting "Why?" gives you:
Performing 'why' on the job...
[and then nothing]
In 6.3 if I put the job on hold and then free it, it starts up. Problem is that the next job (non-cyclic) won't start and has the same 'why' issue. (in 6.2 the only solution was to bounce ^m)
The cyclic File Watch job cycled twice then stopped (correctly) due to a resourse being busy but then failed to restart when the resource was released.
Unix support say there's no errors in any logs so I'm at a loss as to what to do.