Hi ,
I have a ob which has a shared container in it. The job is running fine when ran directly, but through sequencer it is getting hanged.....
In job monitor status it is showing as if it is finished but in director it is still in running state...
And also aborting the job using job cleanup resources option is creating lock horns.
problem running a job which has a shared container
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 16
- Joined: Thu Sep 08, 2011 8:29 am
- Location: hyderabad
problem running a job which has a shared container
Naresh
DataStage Developer
DataStage Developer
-
- Participant
- Posts: 16
- Joined: Thu Sep 08, 2011 8:29 am
- Location: hyderabad
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You are being really parsimonious with the information you're giving.
So, why do YOU think the job is hanging? Is anything happening within the logic that might cause a lock? Is there any database access within the shared container?
So, why do YOU think the job is hanging? Is anything happening within the logic that might cause a lock? Is there any database access within the shared container?
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.