Encrypted passwords environment variables problems..

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
stivazzi
Participant
Posts: 52
Joined: Tue May 02, 2006 3:53 am

Encrypted passwords environment variables problems..

Post by stivazzi »

Hello.
i have some passwords saved in environment variables.
Trying to load them, in some cases (cannot understand which ones) when i read environment variables settings at the beginning of the sequence job, i can see some of them are shown by DS with encrypted value... but some is shown as '' (blank)... never happened to you?
trying to load this strange variable in another sequence job, i can see encrypted value, and all works fine....

Can you help me?

Thanks...
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

I've never seen this behaviour. What default value do you give the job parameter that references this environment variable?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
stivazzi
Participant
Posts: 52
Joined: Tue May 02, 2006 3:53 am

Post by stivazzi »

no default value...
it's environment variable, encrypte... cannot set to $PROJDEF... i just see *******

now i found a walkthrough... i call, from my sequence job which cannot see the variable, the sequence one which sees the variable... and it works!
but i wanted to understand why so a strange behaviour
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You CAN set to $PROJDEF. It's just that encrypted job parameters only echo "*" characters as they're being typed in.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
stivazzi
Participant
Posts: 52
Joined: Tue May 02, 2006 3:53 am

Post by stivazzi »

did it, but setting to $PROJDEF does not solve my problem
narasimha
Charter Member
Charter Member
Posts: 1236
Joined: Fri Oct 22, 2004 8:59 am
Location: Staten Island, NY

Post by narasimha »

Go to the Job Properties of the job, delete the environment variable and re-add it.
This has helped me a couple of times.
Narasimha Kade

Finding answers is simple, all you need to do is come up with the correct questions.
vmcburney
Participant
Posts: 3593
Joined: Thu Jan 23, 2003 5:25 pm
Location: Australia, Melbourne
Contact:

Post by vmcburney »

If a parameter seems to be set in the Administrator and is coming through as blank in the job there is usually a minor misspelling somewhere in the process.
stivazzi
Participant
Posts: 52
Joined: Tue May 02, 2006 3:53 am

Post by stivazzi »

i don't think of misspelling...
variables name imported as job parameters from same environment.
saved in the same way on 2different jobs.
imported not typing, but picking them up from job variables...

i cannot see a misspelling.
Post Reply