Best practices for user defined environment variables.
Posted: Mon Jun 02, 2008 2:14 am
Hi there,
Could please tell me what is best way to maintain user defined variables in DataStage 8.0.
Is it better to create parameter sets or defining user defined variables in datastage admin? if so, what are the pros & cons.
And also one more question,
I have 300 jobs in my project, i have called apt_config_file environment variable in every job, this apt_config_file file path is changed every time when i migrate datastage jobs to deferent environment like QA or Production so now my problem is every time I have to open the job and change the path of the apt_config_file, it is very huge task to open each and every job and changing the path and compile the job. Can anyone suggest how to avoid this type of problems.
Could please tell me what is best way to maintain user defined variables in DataStage 8.0.
Is it better to create parameter sets or defining user defined variables in datastage admin? if so, what are the pros & cons.
And also one more question,
I have 300 jobs in my project, i have called apt_config_file environment variable in every job, this apt_config_file file path is changed every time when i migrate datastage jobs to deferent environment like QA or Production so now my problem is every time I have to open the job and change the path of the apt_config_file, it is very huge task to open each and every job and changing the path and compile the job. Can anyone suggest how to avoid this type of problems.