Parameters at the oproject level:

rjhcc · Post by **rjhcc** » Thu Nov 29, 2007 11:07 am

When setting user defined variables in the Admin. and encrypting passwords, the job(even though using $PROJDEF) will not see the encrypted password and so causes a db access error.

The only way to get around this is to remove the encryption ion ADMIN and type the passowrd in directly.

Is this a bug?

chulett · Post by **chulett** » Thu Nov 29, 2007 11:11 am

What specific 7.x version of DataStage?

singhald · Post by **singhald** » Thu Nov 29, 2007 11:44 am

use #Passord# in the password box in the required stages..

rjhcc · Post by **rjhcc** » Thu Nov 29, 2007 12:36 pm

We're at 7.5.1.

What's the #PASSORD#? If I'm passing to an environment variable, I believe I have to have the $ in front. And I have to assume a typo there-should it not be #$PASSWORD#

chulett · Post by **chulett** » Thu Nov 29, 2007 12:41 pm

The only reason I asked about the version is that early implementations did not handle encrypted passwords properly from what I recall. However, on 7.5.1 you should be 'fine'.

I haven't tried using them myself, so can't reall comment on how it should (or should not) be done.

lstsaur · Post by **lstsaur** » Thu Nov 29, 2007 1:49 pm

Robert,
All my applications using $PROJDEF for encrypted passwords. It's working exactly as expected. No problem at all.

gateleys · Post by **gateleys** » Thu Nov 29, 2007 2:41 pm

Hi Robert,
You have posted a problem, which you think can't be solved as documented, and then you go on to say there is a work around, without actually researching what could have gone wrong.

I completely disagree with your comment that an passwords stored as encrypted do not work. I use 7.5.1 and all database passwords in my site are stored as encrypted in DSParams. And we have had no issue whatsoever with using $PROJDEF for the password parameters.

Or, did you actually paste the 'encrypted' value of the password in the Admin client User variables grid?

.... Of course, that wouldn't work.