JOBCONTROLLER

asitagrawal · Post by **asitagrawal** » Tue Jul 03, 2007 6:11 am

Hi,

In a custom before job routine,

I am determining the Controller of the job,
using DSGetJobInfo(JobHandle, DSJ.JOBCONTROLLER).

Acoording to DSbooks,

Name of the job controlling the job referenced
by the job handle. Note that this may be several job names separated
by periods if the job is controlled by a job which is itself controlled, etc.

But, in my case, am getting just the immediate controller sequences name, not the sequence (Seq1) which is controlling another sequence ( Seq2 ). The job is being controlled by Seq 2 !!

Code: Select all

Seq 1---- > Seq 2 ----> Job 1

JoshGeorge · Post by **JoshGeorge** » Tue Jul 03, 2007 6:32 am

Known Bug I think . You will have to recursively call this API.

kcbland · Post by **kcbland** » Tue Jul 03, 2007 11:45 am

It's a bug, that API returns the name to the immediate controlling job. If the controlling job is itself controlled, you'll need to check that as well. You'll have to attach to the controlling job and then call the API again.

<<Removed the NOT I had originally typed, which shouldn't have been there, brain is fried, hands have mind of their own>>

ray.wurlod · Post by **ray.wurlod** » Tue Jul 03, 2007 1:10 pm

Then the Help is wrong.

DataStage Designer Help wrote:DSJ.JOBCONTROLLER String - name of the job controlling the job referenced by the job handle. Note that this may be several job names separated by periods if the job is controlled by a job which is itself controlled, etc.

chulett · Post by **chulett** » Tue Jul 03, 2007 3:09 pm

Indeed.

ArndW · Post by **ArndW** » Tue Jul 03, 2007 9:20 pm

It is most certainly a bug, I know I had a ticket open for that and ended up having to code a recursive routine to get the whole "family" of a job's parents.

asitagrawal · Post by **asitagrawal** » Wed Jul 04, 2007 2:33 am

ArndW wrote:It is most certainly a bug, I know I had a ticket open for that and ended up having to code a recursive routine to get the whole "family" of a job's parents.

I have also written a recursive routine to get the to the immediate controller.... because I was not getting the results as mentioned in the guide.. so call it a wrong help or a known bug... ...now I know that writing the recursive routine was correct... that is what I was looking for ... Great !

thanks to all