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.
Releasing jobs held by another User
Moderators: chulett, rschirm, roy
Re: Releasing jobs held by another User
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.
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.
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.
-
- Charter Member
- Posts: 822
- Joined: Sat Sep 17, 2005 5:25 pm
- Location: USA
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
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.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.