Passing environmetal variable dynamically

kittu.raja · Post by **kittu.raja** » Tue Apr 05, 2011 9:42 am

Hi,

I have a question on passing environmental variable dynamically (not values).

We are trying to create a common job, which has a common parameter $PASS. This is a multi-instance sequence, where we should get the passwords dynamically from lot other environment variables. We cannot include all the password environment variables in the job properties as there might be new variables added later.

We should use the new variables as required but without making any code changes. We can pass in the parameter to the job dynamically but I believe the sequence would abort if the variable is not defined in the job properties. Is there a way to get around this? Please share your thoughts.

Also note that I cannot have this value stored in a table or file and read it in the run time as these are passwords.

Your help is highly appreciated. Thanks in advance.

jwiles · Post by **jwiles** » Tue Apr 05, 2011 3:29 pm

One method would be to run your job using a sequencer. One (or more if appropriate) of the job parameters would be the name of the environment variable containing the password.

A command activity in the sequencer can echo the password: echo $#variable_name#, and the job activity can pass the output from the command activity as a job parameter to your job.

Of course you should encrypt your password if at all possible. The output from the command activity will show up in the job log.

There may be something that can be used within a BASIC routine as well, but can't think of it at the moment.

Regards

ray.wurlod · Post by **ray.wurlod** » Tue Apr 05, 2011 3:34 pm

There is no limit to the number of parameters that a job may have.

When you add environment variable parameters to a job, you can use special tokens for their default values.

$PROJDEF means "use the default value defined for the project (in the Administrator client"

$ENV means "obtain the value from the executing user's operating system environment (shell)"

$UNSET means "treat this environment variable as unset unless a non-default value is provided when the job run request is issued"

karthi_gana · Post by **karthi_gana** » Sun Feb 26, 2012 3:09 am

where i can find the list of token variables ? i mean in which manual?

i have recently faced an issue. I used environment variable for the password.

when i run the job , it failed with "Login Failed" error message.

I just checked with DSADMIN team and they edited the environment variable and entered $PROJDEF in both the text box. After that the job ran fine.

I really dont understand this. We used the same variable in almost 70 jobs. Do i need to do the above said exercise (like editing the environment variable and entering the $PROJDEF in both the text box) ? is there any way to achive this?

Also, going back to my previous question

where i can find the list of token variables ? i mean in which manual?

chulett · Post by **chulett** » Sun Feb 26, 2012 8:55 am

Token variables? If you mean ones like Ray listed, those three are it and you can find them in Client Guide for the Director or the Designer. If you mean all of the $APT environment variables, I don't recall seeing a manual where they are all listed but you can find them in any job's properties when you add an environment variable from the pick-list.

karthi_gana · Post by **karthi_gana** » Mon Feb 27, 2012 12:14 am

Thanks Craig !

any thoughts on my problem ? Do i need to apply $PROJDEF in all the jobs ?

chulett · Post by **chulett** » Mon Feb 27, 2012 8:10 am

Need to? No, it doesn't sound like it. I would imagine you simply entered the name of the variable incorrectly in that one job. Overall, the use of those tokens like $PROJDEF is certainly a best practice but you'd have to decide if it is worth the time and effort to change it across all jobs.