Page 1 of 2
Job stay in running mode in director
Posted: Tue Jul 22, 2014 11:21 am
by thurmy34
Hi gurus
We are facing the following issue: some jobs are staying "running" in the Director.
When we check the monitor all the stages are green and in the log we can see the sequence main program finished "Ok".
On the server a process usvh is present.
What is your advice?
Thank you.
Posted: Tue Jul 22, 2014 11:50 am
by WesL
Happens from time to time. Check out this technote and see if it helps clear up the issue.
http://www-01.ibm.com/support/docview.w ... wg21390366
Posted: Tue Jul 22, 2014 12:09 pm
by chulett
The technote seems to be specific to all jobs hanging rather than 'some'...
Posted: Tue Jul 22, 2014 1:22 pm
by thurmy34
Hi Wesl
I knew this link , i don't feel confortable running the CLEAR.FILE &PH& command (because it's not clear to me) and like Chulett is't about tree jobs in a project.
Thank you anyway.
Posted: Tue Jul 22, 2014 3:06 pm
by PaulVL
Is it in PROD or a non prod environment where you can play a bit?
Posted: Tue Jul 22, 2014 3:58 pm
by thurmy34
it's a non prod environnement
Posted: Tue Jul 22, 2014 4:56 pm
by ray.wurlod
If you're sure (for example from the log) that the job has finished, clearing its status file from Director will clear the Running status.
Posted: Wed Jul 23, 2014 12:57 am
by thurmy34
I'm ok with that Ray but that i really want it's a way to avoid the problem.
Thank you.
Posted: Wed Jul 23, 2014 6:55 am
by chulett
I'd still look at the &PH& directory in the project and see if it has "a large number" of entries in it. And when you are at a point where no jobs are (legitimately) running in it, do the CLEAR.FILE mentioned. Keeping it pruned down - assuming there are many files there - is actually one way to avoid problems.
Posted: Wed Jul 23, 2014 7:03 am
by thurmy34
Chulett
In the &PH& i have 436 files (is this large ?).
The creation date of the oldest is 14/10/2013 the date of the newest is today.
Thank you
Posted: Wed Jul 23, 2014 7:47 am
by chulett
I don't believe so... still, clear it and see if the behavior you are seeing changes at all.
Posted: Wed Jul 23, 2014 8:12 am
by PaulVL
Create a "CopyOf" job, rename the orriginal to "..._bak", rename the CopyOf to the orriginal name, recompile.
See if the issue persists. If it does not, then you can analyze your "_bak" files. If it does, then you have a larger environmental issue and this freeze might be affecting other jobs, but you just don't know it yet.
Do you have any After Job routines on this job that could still be running?
Posted: Tue Jan 20, 2015 4:08 pm
by thurmy34
Hi All
We're still facing this issue .
Can you help me ?
Regards
Posted: Tue Jan 20, 2015 4:46 pm
by PaulVL
Are you using the grid enablement toolkit?
Posted: Tue Jan 20, 2015 10:54 pm
by chulett
Have you involved support?