Page 1 of 1

Default Values in Parameter Set

Posted: Thu Oct 24, 2013 9:34 am
by iq_etl
We've got 8 generic parameters in a parameter set and each DS job has its own, unique values it may or may not use, is it possible to set up a parameter in the Job Properties that can serve as a default value for one of the generic 8 parameters in the parameter set?

I'm wondering something like if in JOB_A I want to set a default value for the current year I can have a parameter named CCYY, prompt would be parameter_set.PARAM01, and default value would be 2013. So then PARAM01 in the parameter set will default to 2013 when it is being used by JOB_A.

Is there something like that I can do to provide default values for the generic parameters in a shared parameter set?

Thanks!

Posted: Thu Oct 24, 2013 1:45 pm
by ray.wurlod
Use values files to provide different sets of defaults for different circumstances (in your case for different years).

If you make the parameters all environment variables you can create default values in the Administrator client.

Posted: Fri Oct 25, 2013 8:42 am
by iq_etl
The value files look like a good approach.

As I add new value files, will I need to re-compile all of the jobs that use the parameter set whether they use the new value file or not?

Also, to get these values from the value files to show up, how are they assigned within a job? It looks like they're assigned in a Job Activity of a sequence. That, to me, appears that every job executed by the Job Activity will have the defaults of that value file.

Is there a way to assign value files at the job level?

Thanks!

Posted: Fri Oct 25, 2013 8:43 am
by asorrell
I would recommend setting any environment variable in a parameter set to $PROJDEF as a default. That way if you change the environment variable at the project level the jobs will pick up the change without recompilation.

Posted: Fri Oct 25, 2013 8:47 am
by iq_etl
Great suggestion, Andy, and we do this with server info parameters.

Here I'm looking more at a series of generic parameter defaults. So say, JOB_A will have PARAM01 as a year of 2013, but JOB_B may have PARAM01 as some code like D12.

Thanks!

Posted: Tue Oct 29, 2013 12:46 pm
by iq_etl
We are using value files to create default values for testing.

Thanks, Ray!