I am having a problem with sequencer.
when i am running the sequencer it gives a warning
Controller problem: Error calling DSRunJob(ScrubClm.), code=-2
[Job is not in the right state (compiled and not running)]
now even though the job sequencer is calling has been compiled and has worked properly previously but still its giving this error.
I have been facing it for last few days
sequence: Error calling DSRunJob(), code=-2
Moderators: chulett, rschirm, roy
Re: sequencer problem
Did you compile the sequence ?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's the job ScrubClm that's not in a runnable state, not the job sequence. This information is in the error message.
The job ScrubClm may be aborted, or not compiled, or running, or stopped, or crashed. Any of these status values mean that the job is not in a runnable state.
That's why job sequences allow "reset if required, then run" in Job Activities.
The job ScrubClm may be aborted, or not compiled, or running, or stopped, or crashed. Any of these status values mean that the job is not in a runnable state.
That's why job sequences allow "reset if required, then run" in Job Activities.
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.
Re: sequencer problem
But sumeet says the job that sequence is calling is compiled and has worked properly. In his private message too he mentioned that he was able to compile the jobs being called. Thatz was I was wondering.sumeet wrote:I am having a problem with sequencer.
when i am running the sequencer it gives a warning
Controller problem: Error calling DSRunJob(ScrubClm.), code=-2
[Job is not in the right state (compiled and not running)]
now even though the job sequencer is calling has been compiled and has worked properly previously but still its giving this error.
I have been facing it for last few days
-
- Participant
- Posts: 53
- Joined: Wed Nov 05, 2003 8:36 am
-
- Premium Member
- Posts: 385
- Joined: Wed Jun 16, 2004 12:43 pm
- Location: Virginia, USA
- Contact:
I have seen similar behavior in 7.5.1A. After promoting a job from version control to a production project, the job was in a compiled state. The JobActivity stage reported that it could not "Reset if required, then run".
Our work around was to manually run the job after promoting it. The JobActivity action could also be changed to "Run".
Our work around was to manually run the job after promoting it. The JobActivity action could also be changed to "Run".
Chuck Smith
www.anotheritco.com
www.anotheritco.com