Hi,
We have a multi-instance sequencer job which runs every 5 seconds. This in turn calls 20 jobs in 2 batches of 13 job each. It is aborting with the below error message:
Cannot get shared access to executable file for job J7XrtS2Lor (DSOpenJob).
Once this job aborts all further invocation of this job and also other jobs fail with controller problem. Our
1. Can anybody explain the reason for this?
2. What shall we do to avoid this? This job was running perfectly well for some months now.
rgrds
Cannot get shared access to executable file
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 27
- Joined: Wed Apr 11, 2007 12:53 am
Is your problem a reproduceable error? Did you try running it again? Maybe your system was overwhelmed at the time and hence your error. Refer to this post for more clarification.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Maybe that job was still running. Two batches of 13 doesn't equal 20 - maybe your run time calculations were similarly faulty? And every five seconds suggests that the jobs all need to finish very quickly indeed.
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.
-
- Premium Member
- Posts: 27
- Joined: Wed Apr 11, 2007 12:53 am
hi,
During this problem the system resource are almost 95% free. This is a multiinstance job and invocation are done every 5 seconds irrespective of the status of previous invocations.
To solve this we have made major changes in the job design. In the previous design we had xml-input stage which was flattening xml. Though we dont have any stats but decided to get rid of the xml-input stage.
In the current design we are flattening files using a perl prog. now we have a sequncer which call 14 plain loading jobs. We are atill in the process of testing it but till now the results are all ok.
rgrds
During this problem the system resource are almost 95% free. This is a multiinstance job and invocation are done every 5 seconds irrespective of the status of previous invocations.
To solve this we have made major changes in the job design. In the previous design we had xml-input stage which was flattening xml. Though we dont have any stats but decided to get rid of the xml-input stage.
In the current design we are flattening files using a perl prog. now we have a sequncer which call 14 plain loading jobs. We are atill in the process of testing it but till now the results are all ok.
rgrds