If you're not sure where your question goes, start here. I can't get the extact usage of value files. Do we need to create the value files manually? IF yes, a Do we need to enter the path of that file name? I have both parameters and value files in my parameter set. I have never used values files in any of my project. I am just heard this concept. So it may be a too basic question. Post by jwiles » Wed Sep 12, am Need to create the value files manually?
No, but you can a No, just the filename. Post by PhilHibbs » Thu Sep 13, pm My suggestion - and I don't know if this is normal practice or not - is to always use value files. If you have a Parameter Set that is common to all your jobs, and you just want the values to be the same for all of them, then still make a value set file called "Default" or "Common" or some such, and supply that to the job in the shell script that runs dsjob.
That way you can override the values by just creating a new set and supplying that instead, and your different environments can have different config e.
In answer to "how to create the files", a file is automatically created whenever you add a new named entry in the Values tab. Post a Comment. When a file based parameter set is used, the parameter set picks up the contents of the file at the time the job is started. This provides excellent flexibility as long job could manipulate a parameter set file, and leave new parameters for a subsequent job.
The key is that the parameters are not compiled into the job or the parameter set. The following steps detail the creation and use of file based parameter sets. In the Parameters tab, create the parameters and defaults. In the Values tab, put the name of the file in the "Value File Name" column. Specify a file name only. No path component. Click OK and save the parameter set. The contents of the file looks like this:. Click Add Parameter Set and select the newly created parameter set:.
0コメント