Page 1 of 1

Generic Parameter File

Posted: Sun Jan 20, 2008 11:43 pm
by mc_harsha
All,

We have around 50 jobs, where we are using one generic parameter file.

Generic parameter file contains values for the 50 variables.

We need to use these values in column derivation of our jobs.

Not all of the job will use all of the variables.

So, My question is Best method to use the generic parameter file.

- Read the variable in Shell script and pass it through job parameter in DS Job command
-Read the variable using look up with dummy look up key
-Read it through routines..

Can you guys provide me best solution with respect to implementation as well as maintainance?

Posted: Mon Jan 21, 2008 12:25 am
by chulett
Use dsjob first to get a list of all parameters defined in the job. Pull any matching parameter names from your 'generic file' and only pass those to the job when you launch it.

:? Or are we not talking about Job Parameters here? If not, please be more clear about the nature and usage of these 'variables'.

Posted: Mon Jan 21, 2008 11:39 am
by kduke
We do exactly this. We have parameter values in 6 types of files. So if you have a parameter jpTargetUser then it can get set in these files. Assuming the job name is JobA and the instance id is Instance1.

1. JobA.Instance1_#jpTargetUser#.prm
2. JobA.Instance1.prm
3. JobA_#jpTargetUser#.prm
4. JobA.prm
5. GlobalParams_jpTargetUser.prm
6. GlobalParams.prm

Here is the line you need in one of these files.

jpTargetUser=etluser

You need to have comment lines to keep track of these.

Posted: Mon Jan 21, 2008 11:40 am
by kduke
We use a scheduler like Control M called Zena. This helps implement faster in Zena. We have a script which can create the prm files by calling dsjob like Craig suggested.