Releasing jobs held by another User

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
pavankvk
Participant
Posts: 202
Joined: Thu Dec 04, 2003 7:54 am

Releasing jobs held by another User

Post by pavankvk »

When ever the designer hangs with a job opened, i kill it. and when opening the same job it gives the error message.

i know that there is something like releasing locks. can you let me know. i am using 7.5 ee edition.
kool78
Participant
Posts: 104
Joined: Sat Aug 20, 2005 2:02 pm

Re: Releasing jobs held by another User

Post by kool78 »

pavankvk wrote:When ever the designer hangs with a job opened, i kill it. and when opening the same job it gives the error message.

i know that there is something like releasing locks. can you let me know. i am using 7.5 ee edition.

hi

Have u tried

director->Job->CleanUp Resources.
iwin
Premium Member
Premium Member
Posts: 99
Joined: Mon Apr 11, 2005 9:20 pm

Post by iwin »

Hi pavankvk,
Basically you can unlock the jobs by two ways:
1) As kool78 said you can release or unlock the jobs from Director.
2) In Administrator, at command line go to DS.TOOLS and select option 5 and enter the pid of the job to release.

I consider these to be the safe methods, instead of killing the Job and breaking the head.
pavankvk
Participant
Posts: 202
Joined: Thu Dec 04, 2003 7:54 am

Post by pavankvk »

i tried cleaning up resources.it never worked. and i also remember trting the pid method..but they didnt help
us1aslam1us
Charter Member
Charter Member
Posts: 822
Joined: Sat Sep 17, 2005 5:25 pm
Location: USA

Post by us1aslam1us »

Hi pavan,

If you can paste the error message someone can answer that properly rather than guessing.Anyway you try to logout of all the process through the director,sometime this will be a problem .

Thanks
Sam
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

And lose the habit of using kill on any DataStage process. It only ever leads to messy cleanup problems. For example, how do you know you correctly identified all child, sibling and parent processes?

Craft your job designs so that they don't hang in the first place.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply