DSXchange

Posted: **Thu Nov 05, 2009 11:29 am**

One of the parallel job is showing weird status in director.
It shows Running status, in logs it shows this message:

main_program: Step execution finished with status = OK.

From unix it also shows as running when I grep for the PID.

But when I ran this command from Unix I get some weird results

Code: Select all

$DSHOME/bin/dsjob -jobinfo myproject myjob

Job Status      : RUNNING (0)
Job Controller  : not available
Job Start Time  : Wed Nov  4 11:29:22 2009
Job Wave Number : 1
User Status     : not available
Job Control     : 0
Interim Status  : NOT RUNNING (99)
Invocation ID   : not available
Last Run Time   : Wed Dec 31 18:00:00 1969 ---- weird!
Job Process ID  : 13713524
Invocation List : myjob
Job Restartable : 0

Also the DATA.30 file is still being updated in RT_LOG2343
-rwxrwxr-x 1 dsadm dstage 96256 Nov 5 11:20 DATA.30

Is the RT_LOG2343 showing signs of corruption?

Posted: **Thu Nov 05, 2009 11:43 am**

Sometimes it does that but to remove that running status go to director under the job tab click on cleanup resources select your job under that and kill it.Then click on clear status file under job tab and it would reset the status from running to compiled.

Posted: **Thu Nov 05, 2009 12:20 pm**

Do you have any After-Job subroutine in the job

Posted: **Thu Nov 05, 2009 3:46 pm**

BradMiller wrote:Sometimes it does that but to remove that running status go to director under the job tab click on cleanup resources select your job under that and kill it.Then click on clear status file under job tab and it would reset the status from running to compiled.

Okay, issue was resolved , thanks.

we logged out process using cleanup resources from director.
cleared the log file.
cleared the status file.
compiled the job.

Thanks

Posted: **Thu Nov 05, 2009 4:32 pm**

This behaviour usually occurs because the job is still receiving and logging warnings from, for example, a connected database server.

Posted: **Fri Nov 06, 2009 10:28 am**

ray.wurlod wrote:This behaviour usually occurs because the job is still receiving and logging warnings from, for example, a connected database server.

I also thought of the same thing and ran the logsum command to find out if any Warnings were being generated for this job.

$DSHOME/bin/dsjob -logsum -type WARNING -max 10 myproj myjob

I was only able to capture 3 warnings ( which were also visible from Director). This job did not have any Database connection, only filesets writing to sequential file.

Not sure why it was still writing to log even though job was seen as completed on Designer and Job Monitor, but it was still writing to log DATA.30.

DSXchange

Director status showing job as running.

Director status showing job as running.