Oh, trust me, they do!danjm wrote:I'm understanding the 'bottom line' to be that DS does not use 'operating system environment variables' at all then (IE: it does not read and use their valuest at runtime)
Just not the ones YOU want to use for your jobs. Just the ones they uses for their own engine.
But then it makes the job much more portable. The way Windows handle their environment variables are entirely different than the way UNIX handle their. A job is expected to be able to run on both platform with VERY MINOR changes.
This is what a job parameter is for. To allow you to pass on to the job any difference in values you want to employ for that particular run without recompiling the job itself. You can pass different values using a third party scheduler tool, or with Parameter Manager as plugged by someone else in this thread. Just do not expect that the job parameter values will change when migrated between projects, at least for now.If I have to edit the job to use modified environment variables then there is no advantage over simply modifying string values in the job! I've still modified the job so I have no guarantee of tested repeatability at runtime. Once you edit ANYthing, you've possibly altered something else unintentionally.
-T.J.