topic Re: tRunJob :Use dynamic job option Not Work for jobs with Dynamic names in Talend Studio

tRunJob :Use dynamic job option Not Work for jobs with Dynamic names

Anonymous — Thu, 25 Jul 2013 11:47:47 GMT

Hi All
TOS 5.2.1
I checking idea of using control table (in Oracle) for running Talends jobs dynamically.
Have something like in tOracleInput:
Select job_name from A_JOB_CONTROL a
where a.flag_active ='Y'
order by job_type , job_sub_type , order_run
-> -> java
--iterate >
and then tries to call tRunJob
with
Use dynamic job option
Context job : context.CONTEXT_JOB
but get Errors:
Parameter (Job) is empty but requied
Parameter (Context) is empty but requied
But because Use dynamic job option checked , textbox for job is disabled.
When I press continue I got :
Exception in component tRunJob_3
java.lang.RuntimeException: The child job named csv_000 is not in the job list.
but csv_000 job exsits for sure (in root folder)!!
What is wrong ?

Re: tRunJob :Use dynamic job option Not Work for jobs with Dynamic names

alevy — Thu, 25 Jul 2013 13:59:56 GMT

Screenshots of your settings are always helpful...

Re: tRunJob :Use dynamic job option Not Work for jobs with Dynamic names

Anonymous — Fri, 26 Jul 2013 12:31:57 GMT

I tried add to name of job in variable quotes :"csv_000"
it doesnot help

Re: tRunJob :Use dynamic job option Not Work for jobs with Dynamic names

alevy — Sat, 27 Jul 2013 09:32:55 GMT

Just click on the ... button and select all the jobs that you want the tRunJob to be able to run.

Re: tRunJob :Use dynamic job option Not Work for jobs with Dynamic names

Anonymous — Mon, 29 Jul 2013 03:06:09 GMT

Hi,
Please see the online component reference tRunJob.
Once there is empty in drop down list, save your jobs(parent and child) and close it. Re-open it to see if this issue repro again.
Best regards
Sabrina

Re: tRunJob :Use dynamic job option Not Work for jobs with Dynamic names

Anonymous — Mon, 29 Jul 2013 09:29:35 GMT

Just click on the ... button and select all the jobs that you want the tRunJob to be able to run.

Great !!! - need list of ALL jobs : j_test_catcher;a_fail;csv_000
THANKS
from error message : job named csv_000 is not in the job list
I could assume that ALL jobs which will be runn dynamically should be in list.
One more question left :
Still left :
Parameter (Context) is empty but requied
When I press continue it works ok
I put for test there also any string value : "0" - it works , 12 - works , #@@#%- works
from Doc :
Context :
If you defined contexts and variables for the Job to be run by the tRunJob, select the applicable context entry on the list.

My goal is to run all jobs in context specifiled in Head job.
(to be able quickly swith between test/dev/prod in one place)
For this in trunJob I put
Transmit whole context on checkbox ON :

Could you pls say few words what should be in Context textbox ?
Now for me it is Not clear from Documnetation

Re: tRunJob :Use dynamic job option Not Work for jobs with Dynamic names

alevy — Mon, 29 Jul 2013 23:44:00 GMT

I think with "Transmit whole context" checked you'll get the result you want and you can just leave the Context textbox as Default.

Re: tRunJob :Use dynamic job option Not Work for jobs with Dynamic names

Anonymous — Tue, 24 Nov 2015 22:39:40 GMT

Hi all,
please help me in below scenario,
i want to run sub jobs one by one but without checking the job option in tRunjob and before entering into tRunjob i want to mention like which sub job has to run first, whether all has to be run or only selected sub jobs and for this i have created one table which gives status column it has to pick which is pending.

Re: tRunJob :Use dynamic job option Not Work for jobs with Dynamic names

Anonymous — Wed, 25 Nov 2015 09:10:03 GMT

Hi,

i want to run sub jobs one by one but without checking the job option in tRunjob and before entering into tRunjob i want to mention like which sub job has to run first, whether all has to be run or only selected sub jobs and for this i have created one table which gives status column it has to pick which is pending.

It seems you want execution order of subjobs. Have you tried to use the onsubjobOk link?
subjob1-->OnSubjobOk-->tRunJob-->OnSubjobOk-->subjobXXX
Best regards
Sabrina