MultiInstance Sequncer failing with Error code 255
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Try removing -wait from the dsjob command. Technically -wait and -jobstatus are incompatible options. The -jobstatus option will still cause the command to wait until the job completes, so that it can report the job status.
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.
Hello,
I m trying to explain the issue once again and Hope it helps.
I have a multi Instance Job. At same time 2 instances of the same job having different invocation ID are running in Parallel. Most of times, Jobs runs with Success i.e. from 20-July till today Job failed only once.
My Analysis is:-
Sometimes both the instances get executed at exact same time and first instance gets the control and executes while the second instance doesn't get the handle and job aborts. While re-running, the failed jobs again, it run successfully
My Question:-
Do I need to make any change in the environment level to increase the wait time or some other setting which will make both the instances of MultiInstance Job execute in Parallel.
Regards
Neeraj
I m trying to explain the issue once again and Hope it helps.
I have a multi Instance Job. At same time 2 instances of the same job having different invocation ID are running in Parallel. Most of times, Jobs runs with Success i.e. from 20-July till today Job failed only once.
My Analysis is:-
Sometimes both the instances get executed at exact same time and first instance gets the control and executes while the second instance doesn't get the handle and job aborts. While re-running, the failed jobs again, it run successfully
My Question:-
Do I need to make any change in the environment level to increase the wait time or some other setting which will make both the instances of MultiInstance Job execute in Parallel.
Regards
Neeraj
The problem here might lie not in the concurrent execution of job sequences, but the way that DataStage parameter set files are opened. The parameter set files might be opened in exclusive mode for reading, and this could theoretically cause sporadic issues. I've started literally hundreds of concurrent instances in projects before without this problem, but they didn't use parameter sets.
</a>