Datastage job still in "Running" state -- after us

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
datisaq
Participant
Posts: 154
Joined: Wed May 14, 2008 4:34 am

Datastage job still in "Running" state -- after us

Post by datisaq »

Hi Datastage Experts,
I have a ran a datastage job sequence through "Autosys Utility" two days before which will trigger a datastage job(which do the loading into tables) , still the job is in running state. But in autosys the job status is showing as "failed", i have used the "kill" command to kill the job but still the same issue continues.

I contacted to the support guys for our project they couldn't able to figure out the issue. In datastage job it's not showing any warnings/fatal error just it's showing as "waiting for job to finish".

Please let me know what might be the issue Or Is there any other way to kill that job??

Thanks in advance
IBM Certified - Information Server 8.1
priyadharsini
Participant
Posts: 40
Joined: Mon May 11, 2009 12:19 am
Location: Madurai

Post by priyadharsini »

Use cleanup resources in director and clear the status file.
datisaq
Participant
Posts: 154
Joined: Wed May 14, 2008 4:34 am

Post by datisaq »

i have cleared the status file and used clean up resources also but no success..
IBM Certified - Information Server 8.1
Vinothbaskaran
Participant
Posts: 22
Joined: Mon Aug 25, 2008 4:01 am

Post by Vinothbaskaran »

You should be able to clear any locks on the job by logging into UV with 'dsadm'. Please follow the below steps.

1. Go to DSEngine directory
2. Execute .dsenv
3. Execute bin/uvsh, this will log in to UV.
4. Type list.readu and find the user id for the job in question
5. type "unlock user userid all"

This will clear all locks and you should be able to stop the job.
Vinothbaskaran
Post Reply