sequence: Error calling DSRunJob(), code=-2

sumeet · Post by **sumeet** » Tue Oct 11, 2005 9:51 pm

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

sun rays · Post by **sun rays** » Tue Oct 11, 2005 10:08 pm

Did you compile the sequence ?

ray.wurlod · Post by **ray.wurlod** » Wed Oct 12, 2005 3:08 am

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.

sun rays · Post by **sun rays** » Wed Oct 12, 2005 9:03 am

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

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.

sivatallapaneni · Post by **sivatallapaneni** » Wed Oct 12, 2005 11:00 am

I think he is hitting the T30 file limit. Sumeet do you have lot of jobs running during that time?

Can you check the uvconfig file for the "T30FILE" entry and see what is the value. The uvconfig file is in the .dshome directory.

chucksmith · Post by **chucksmith** » Thu Oct 13, 2005 5:58 am

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".

DSXchange

sequence: Error calling DSRunJob(), code=-2

sequence: Error calling DSRunJob(), code=-2

Re: sequencer problem

Re: sequencer problem