Environment Variable- Refresh
Moderators: chulett, rschirm, roy
Environment Variable- Refresh
Hi Everybody,
We are using environment variables for
1. Database related values like Server Name, UserID, Password etc.
2. Files related activities, InputPath, Out Put Path etc.
Everything was fine till now.
We were expecting that we can modify the values of Env values and that can be reflected in our jobs.
However it seems that eventhough the env values are changed but they are not refreshed in our jobs.
Do we need to restart DS once we modify the Env values.
Or there is anything we are missing.
Any input will be highly appreciated.
Thanks and regards,
Munish
We are using environment variables for
1. Database related values like Server Name, UserID, Password etc.
2. Files related activities, InputPath, Out Put Path etc.
Everything was fine till now.
We were expecting that we can modify the values of Env values and that can be reflected in our jobs.
However it seems that eventhough the env values are changed but they are not refreshed in our jobs.
Do we need to restart DS once we modify the Env values.
Or there is anything we are missing.
Any input will be highly appreciated.
Thanks and regards,
Munish
MK
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
No. There is no need to restart the DataStage Services.
Once you change the values of the Env variables in the properties window of the administrator, are you clicking on "OK" button on the properties window? Only then will the change be registered.
Whale.
Once you change the values of the Env variables in the properties window of the administrator, are you clicking on "OK" button on the properties window? Only then will the change be registered.
Whale.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Premium Member
- Posts: 1255
- Joined: Wed Feb 02, 2005 11:54 am
- Location: United States of America
Exactly, you need to use $PROJDEF.Munish wrote: We have about 12 different env variable.
So if one job is using all of these variables
we should have $PROJDEF as default for every variable.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
$PROJDEF must be the default value for the job parameter, in the job.
The environment variable (set up in Administrator) must have a "genuine" default value - that is, not $PROJDEF, $ENV or $UNSET.
The environment variable (set up in Administrator) must have a "genuine" default value - that is, not $PROJDEF, $ENV or $UNSET.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Hi,
'$PROJDEF' is working fine.
However it is not working with Passwords.
For encrupted password environmen variable, I have to delete and reload the environment variable.
Any Thoughts !!!!
As for Narasimha, I am not sure why it did not worked initially. I restarted my Datastage and it was bang on.
Thanks,
Munish
'$PROJDEF' is working fine.
However it is not working with Passwords.
For encrupted password environmen variable, I have to delete and reload the environment variable.
Any Thoughts !!!!
As for Narasimha, I am not sure why it did not worked initially. I restarted my Datastage and it was bang on.
Thanks,
Munish
MK
Password can be set with $PROJDEF
Hi Munish
I think you brought up the issue of not being able to use the password with $PROJDEF in some other place. You can do one thing.... Whenever you type the default value for password, type it as $PROJDEF only. You will be able to enter it in encrypted format only (*s). But you can use that.
I think you brought up the issue of not being able to use the password with $PROJDEF in some other place. You can do one thing.... Whenever you type the default value for password, type it as $PROJDEF only. You will be able to enter it in encrypted format only (*s). But you can use that.
Arnab
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can use cut-and-paste. Put $PROJDEF into the Description field (clear), cut it from there (Ctrl-X) and paste it (Ctrl-V) into the Password or Default Value field.
I presume you're aware that to enter a default value for an encrypted parameter you have to double-click in the Default Value cell to open the dialog where you have to enter the value twice?
I presume you're aware that to enter a default value for an encrypted parameter you have to double-click in the Default Value cell to open the dialog where you have to enter the value twice?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.