Can environment variables be copied into another project?
Posted: Fri Mar 31, 2006 12:15 pm
Hi there,
Job parameters can be defined in Datastage Administrator with Project Properties\Environment Variables and used as job parameters in Datastage Designer. My problem is when these parameters are defined in a Datastage project, can they exported and imported into another project? Such as from development environment, to test environemt.
When a job uses the variable as job parameter and is exported and imported int another project, it can be compiled with the following error:
Environemt variable '$Src...' defined in job parameters but not defined in project.
Why there is no "Help Text" column in "Environment Variables"? This is not good at all, because when the variable is added to a job, do you have to type the Help Text again and again?
Another issue is "Environment Variables" in Administrator have only two datatypes: String and Encrypted, but much more in Designer, like Integer. Why that's the case?
Thanks,
Job parameters can be defined in Datastage Administrator with Project Properties\Environment Variables and used as job parameters in Datastage Designer. My problem is when these parameters are defined in a Datastage project, can they exported and imported into another project? Such as from development environment, to test environemt.
When a job uses the variable as job parameter and is exported and imported int another project, it can be compiled with the following error:
Environemt variable '$Src...' defined in job parameters but not defined in project.
Why there is no "Help Text" column in "Environment Variables"? This is not good at all, because when the variable is added to a job, do you have to type the Help Text again and again?
Another issue is "Environment Variables" in Administrator have only two datatypes: String and Encrypted, but much more in Designer, like Integer. Why that's the case?
Thanks,