Status=99 (Job not running)

saraswathi · Post by **saraswathi** » Wed Jun 20, 2007 1:24 am

I have ran a server job through sequencer. I'm getting the error
status=99(Not running).

ray.wurlod · Post by **ray.wurlod** » Wed Jun 20, 2007 1:35 am

Welcome aboard. :D

Clearly you have NOT "ran a job through sequencer".

Try compiling the job and running it in isolation. Then try running it from the job sequence (note: not "sequencer"). Tell us what appears in the job sequence's log.

joesat · Post by **joesat** » Wed Jun 20, 2007 2:21 am

what sarawathi means is that she ran a particular job sequence, but one of the job finished with the status=99. i am experiencing the same problem. because of this, the next job in the sequence throws an error "Error fetching job status" in the description panel of Datastage Director...

i have compiled the sequence and executed it, it stops at the same job. but curiously the job executes successfully in isolation, but stops in the sequence!

what does one have to do? please help...thanks!

ArndW · Post by **ArndW** » Wed Jun 20, 2007 2:26 am

Is there additional information in the log file when you reset the job, i.e. and entry titled "from previous run..."?

joesat · Post by **joesat** » Wed Jun 20, 2007 3:06 am

This is the log corresponding to the failed job in the sequence,

JobSeq.93.JobControl (DSWaitForJob): Job IndividualJob.93 has finished, status = 99 (Not running)

Note: JobSeq is the name of the sequence and IndividualJob is the name of the job, 93 is the run id

joesat · Post by **joesat** » Wed Jun 20, 2007 3:08 am

This is the log corresponding to the failed job in the sequence,

JobSeq.93.JobControl (DSWaitForJob): Job IndividualJob.93 has finished, status = 99 (Not running)

Note: JobSeq is the name of the sequence and IndividualJob is the name of the job, 93 is the run id

ArndW · Post by **ArndW** » Wed Jun 20, 2007 3:35 am

Joe - did you try the reset on the job?

saraswathi · Post by **saraswathi** » Wed Jun 20, 2007 8:20 am

Yes i have reset the job, but it is still showing the same

saraswathi · Post by **saraswathi** » Wed Jun 20, 2007 8:35 am

I deleted the job and imported the .dsx file freshly and compiled it. Now when I compile the job and run it individually the job remains in the in the compiled state and doesnt execute

panchusrao2656 · Post by **panchusrao2656** » Wed Jun 20, 2007 9:02 am

Are you using any invocationID when you are calling from the sequencer, might be job with that particular invocationID having the status 99

VijayaHarsha · Post by **VijayaHarsha** » Wed Jun 20, 2007 4:02 pm

I had the same problem when I was running the job sequence, which had a routine in it. I mistyped one of the input parameters while calling the routine in the job sequence which resulted status 99 error. Once I corrected it, the routine was running fine.

saraswathi · Post by **saraswathi** » Wed Jun 20, 2007 10:56 pm

All the input parameters in the routine are correct only. I think the problem is in a server job. When I try to run the compiled job individually, it's showing unable to return an attached job and doesnt execute.

joesat · Post by **joesat** » Thu Jun 21, 2007 12:08 am

can someone explain what "Unable to return attached job" means?

ray.wurlod · Post by **ray.wurlod** » Thu Jun 21, 2007 3:08 am

Try taking a copy of the job, and compiling and running that. If that works, delete the bad one, rename the new one and recompile.

joesat · Post by **joesat** » Thu Jun 21, 2007 5:53 am

have tried that...still same problem