Datastage Sequence Jobs-Forced to use Environment Variables

J.Calvo · Post by **J.Calvo** » Thu Oct 15, 2009 3:11 am

Hi, I'll tray to explain:

In our version of Datastage (8.0.1), when we try to use sets of parameters in sequence jobs, the value is lost in the server jobs inside it,

When a job run inside it the value is allways the prefefined for the parameter and not is the correct.

chulett · Post by **chulett** » Thu Oct 15, 2009 5:26 am

So... this issue is specific to using parameter sets rather than 'regular' parameters? And by 'lost' you mean they are not passed, the job always takes the default value - is that correct?

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Thu Oct 15, 2009 5:26 am

Open the job activity and see what the job's parameters are set as. Maybe they are set to default.

J.Calvo · Post by **J.Calvo** » Thu Oct 15, 2009 9:07 am

That is the problem, I write the parameters values, in sequential job execution, and in it the parameters would be transferred to the server jobs but that is the bug... it fails.

chulett · Post by **chulett** » Thu Oct 15, 2009 9:20 am

Please verify if this is a problem just with parameter sets or if you have the issue with 'normal' job parameters as well.

J.Calvo · Post by **J.Calvo** » Thu Oct 15, 2009 9:49 am

Ok, chullet, i have now other complicated and important tasks but, if i solve it i'll verify this point. (But With Parameters I think exists the same problem)