Hi
In our project we are using DataStage environment variables for parameterising the Database server name, schema name, log file path. Is it the right way of parameterising these variables or is there any other better way to achieve this ?? If we are changing the value of an environmental variable in Administrator, will that have a cascading effect across jobs using that variable or should we open every job explicitly and change the default value ?? Any suggestions and inputs most welcome...
Vignesh.
Parameterising job variables
Moderators: chulett, rschirm, roy
That's certainly one way to do things. Question for you - what specific version of 7.x are you running? Environment Variables were a little 'broken' in the early releases, but fixed in later ones... I think you need at least 7.1 before they work fully. 
Before the fix, all jobs using them would need to be recompiled to pick up any changed value.
It would be mentioned in the readme.
Before the fix, all jobs using them would need to be recompiled to pick up any changed value.It would be mentioned in the readme.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Hi Vignesh,
Good question. I hope you know very well about environment variables and what is use of environment variables. the environment variables to control how jobs operate on a UNIX system. In addition to providing required information, environment variables can be used to enable
or disable various DataStage features, and to tune performance settings.
chulett added that new version 7.1 they fixed the environments variables broken.
I hope you need 7.1 or 7.5.
Thanks
man
Good question. I hope you know very well about environment variables and what is use of environment variables. the environment variables to control how jobs operate on a UNIX system. In addition to providing required information, environment variables can be used to enable
or disable various DataStage features, and to tune performance settings.
chulett added that new version 7.1 they fixed the environments variables broken.
I hope you need 7.1 or 7.5.
Thanks
man
Parametertizing is very good and this leads to....
1. Assure you are using relative and not absolute pathing such as via a .ini file
2. Environment variables start with the dsenv file in youe $DSHOME and impact all Projects on the server in question.
Then for a specific Project you can go in Administrator and this impacts all Jobs in that Project and overrides the dsenv for redundant entries.
Then for a specific Job you can go in Designer Job Properties and this impacts only Job and overrides the dsenv and Administrator for redundant entries.
You manipulate for your needs.
1. Assure you are using relative and not absolute pathing such as via a .ini file
2. Environment variables start with the dsenv file in youe $DSHOME and impact all Projects on the server in question.
Then for a specific Project you can go in Administrator and this impacts all Jobs in that Project and overrides the dsenv for redundant entries.
Then for a specific Job you can go in Designer Job Properties and this impacts only Job and overrides the dsenv and Administrator for redundant entries.
You manipulate for your needs.