I have a unix script that calls a DataStage job. this job runs fine when it runs on it's own. I know the script is good because it runs other jobs fine. Here is the error when the script calls the job:
Error running job
Status code = -2 DSJE_BADSTATE.
Not much to go on. Anyone see this problem before?
Prob lem running UNIX script for a DataStage job
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 437
- Joined: Fri Oct 21, 2005 10:00 pm
Re: Prob lem running UNIX script for a DataStage job
It looks like you job needs to be in a runnable state when the script attempts to execute the job. You could catch this error and attempt to reset the job if it is in a bad state.
Keith Williams
keith@peacefieldinc.com
keith@peacefieldinc.com
-
- Participant
- Posts: 147
- Joined: Sat Apr 30, 2005 1:23 am
- Location: Bangalore,India
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
"Not in a runnable state" includes "already running". Check that you don't have the script trying to start the same job twice, or two scripts trying to start the same job at similar times.
Otherwise check that the job status is one of "finished", "finished (see log)", "validated", "validated (see log)", "compiled" or "has been reset". These are the only status values that indicate that the job is in a runnable state.
Otherwise check that the job status is one of "finished", "finished (see log)", "validated", "validated (see log)", "compiled" or "has been reset". These are the only status values that indicate that the job is in a runnable state.
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.