Setting user defined Environment Variable to $ENV

thanush9sep · Post by **thanush9sep** » Mon Nov 23, 2009 12:48 am

Hi All

I have created a user defined Environment Variable called ORA_PWD and set the default value as $ENV

In the .profile I gave ORA_PWD=aaa; export ORA_PWD
if I put echo $ORA_PWD, I am able to see the value for ORA_PWD as 'aaa'

I used ORA_PWD = $ENV as job parameter in my job which contains ORACLE stage as source

I got the following error while I clicked the view button

---job parameter '$ORA_PWD' cannot take the special value '$ENV' when executing View Data. Only literal String values are allowed

when I ran the job I got the following error

---Missing Parameters $ORA_PWD [$ENV].

1. My question is do I have to restart the server after declaring ORA_PWD=$ENV?

2. Am I missing something while trying to get a value from the environment. If yes what is it?

I just went to almost all the post here, I guess I am missing something

ray.wurlod · Post by **ray.wurlod** » Mon Nov 23, 2009 3:55 am

In 7.5x2 View Data does not accept environment variable parameters with $PROJDEF, $ENV or $UNSET as default values at all.

You should not need to start the server. However, you probably do need to create an environment variable called ORA_PWD in the Administrator client. Set that one's default value as $ENV also.

thanush9sep · Post by **thanush9sep** » Mon Nov 23, 2009 4:29 am

Thanks Ray

This is what I did to get the value of ORA_PWD from the Environment

I assigned a value for variable called PWD=aaa and then used the below command in the .profile
PWD=aaa;
export $PWD (dont know whether this is necessary or not)

dsadmin -envset ORA_PWD -value $PWD ProjectName

in the Administrator I kept ORA_PWD as string and DataStage took care of the rest

and each and every job I used $PRODEF for ORA_PWD

if I change PWD value in the .profile then ORA_PWD will change automatically in DataStage

ray.wurlod · Post by **ray.wurlod** » Mon Nov 23, 2009 4:33 am

Not unless there's at least one reference to $ENV as a default value - either in the Administrator client or in the job parameters grid.

thanush9sep · Post by **thanush9sep** » Mon Nov 23, 2009 4:42 am

Sorry Ray

I did not understand.

chulett · Post by **chulett** » Mon Nov 23, 2009 7:45 am

The value you assign the environment variable in the Administrator should be $ENV and the default value of that environment variable when you add it to your job should be changed to $PROJDEF. In the job.