Many thanks for your response.
I have already tried that and it uses the "Prod" context for the parent job, but then it uses the default context (in my case "Dev") when calling the sub-job.
I have a same issue. And I need the solution.
But I found, If this value for the context is in constant. Like "dev", "Production" And this works.
Mais if we use a variable for context, it dose not work.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Watch the recorded webinar!
Part 2 of a series on Context Variables
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema