stats et logs in table with tcontextload in project parameter

[lemufty]

hi,
i develop job  which work. so i would like to catch stats et logs in table STATS and LOGS. 
but i configure project parameter.but i launch a job in ms_dos.il can't see the parameter.
so it don't load stats et logs into table.
 below screnshot


 





it can not see db connexion and can not load the table stat


thank you for your help

[Anonymous]

This is caused by your context variables not being pre-set in your job. The AMC and loading context variable values at the start of a job do not mix very well. There are a couple of ways to get round this. Either load your context variables into a parent job and then use that parent job to call the job you are having trouble with (setting "transmit whole context") or use the AMC components instead of doing it in the project settings. The easiest way of doing that is to use a Joblet to call the tLogCatcher, tStatCatcher and tFlowMeterCatcher all linked to tHash components. Use a tPostJob component to empty the tHash components into the database tables or files at the end of the job. tPostJobs are always called so you won't lose logs.

[lemufty]

think you for your answer,
so in my example when i build a job, i don't put script context because my context came from extern file.
this is my script to launch the job in ms dos:
J_RDD_DPI_CRM_Plateforme_run.bat --context_param globalCtxFile=C:\TFS\PID\Dev\CRM\Config\DEV\config.properties 
but when i launch le job in talend, i have no problem are  table log et stats are loaded.

[Anonymous]

I'm guessing that when you launch this in Talend Studio your context variable values are already set. If they have any values set, they will be used instead of imported ones. Clear any values set for the context variables in the Studio and try it again. It will fail.

[lemufty]

but when i add connexion parameter. i have not error.

or i don't want to put connexion parameter because it is already in my globalCtxFile

[Anonymous]

That is because the Talend job is started with knowledge of your connection details. The AMC starts logging as soon as the job starts. For some strange reason Talend is configured to load context variables (implicit context variables and loading using the tContextLoad) after the AMC has started logging. I personally think this needs sorting out.