We have run into an issue where we need to pull in a value from a source, could be flat file or database table, doesn't matter to us. However I would like to have that value saved as a global variable that is accessible to any other job. Is something like this possible? Could execute something at the command line to set an evironment variable value or other variable value that I can then use in a parallel job?
To be fair I COULD do this via a file read in a sequence job, and pass that value down to all other jobs as a job variable. That would entail me having to add that job variable to every job. *NOTE: I've had issues passing values to specific parameters in a parameter set from a sequence job, hence my comment to add the job variable to each job as opposed to using a parameter in a set.
I read on here some time back regarding setting a job to read-only by setting a value for a job in a database table that stores job information. I could have misunderstood but is this a thing? Is there a database that stores various datastage project information? If so could someone point me in the right direction? My googlefoo must not be that good as I have yet to determine this on my own.
![Embarassed :oops:](./images/smilies/icon_redface.gif)
UPDATE: It looks like the datastage project and job information is stored in our XMETA database. Trying to determine what tables contain the projects environment variables.