global variable

[acool]

Hi everyone,

My database password changes once a month, is there any way I can create a global stage variable so that all jobs in the project can use it as the database password?

[kcbland]

Only by working with job parameters can you achieve such a goal. You can put a job parameter as the password and supply the appropriate value at runtime. Environment variables work the same as parameters, you'll have to declare the envinronment variable as a job parameter.

I don't believe a macro works, but if it does, then you might have that as an option as well. The point is the same, you must feed each process with the approriate values.

If you can setup a trusted connection via the userid that jobs run under, then you bypass this requirement.

[ketfos]

Hi,
Another way could be creating a Unix Shell Script, pass the user id and password values from your database to this script and let the script invoke the datastage job via dsjob command with all parameters.

Ketfos

[richdhan]

Hi,

You can create an environment variable for the Database password and add the environment variable to the job parameter list in all your jobs. Set the value to $PROJDEF which means the project default value is used for the parameter.

For each month change the value of the environment variable and $PROJDEF ensures that the new value is used in your jobs.

HTH
--Rich

Pride comes before a fall
Humility comes before honour

[chulett]

Before attempting to use Environment Variables as Rich mentions, make sure you are running at least the 7.1 version. From what I recall, the original 7.0 release added the capability to use them, but you had to recompile the job to get it to notice a value change.