Changes of parameters in admin,not relected in job

[raji]

Hi,

In my project I am facing the following issue:

We developed datastage server (7.5.2) jobs in AIX environment(UNIX).

The jobs are running fine in Development environment. When we change the password(encrypted) in the administrator of same environment, its not reflected in the Job and its taking the old password.

But when we delete the parameter in the job properties for the password and again add the same parameter from the environment settings, it works fine.

If anyone has encountered any such kind of issues before, please help me out.

Thanks in advance

[chulett]

What default value are you using in your jobs - the actual value from the Administrator or $PROJDEF?

[raji]

Thanks for your prompt reply.

I am using $PROJDEF.

[ray.wurlod]

Have you reported this apparent bug to your official support provider? If so, what response did you get?

[raji]

No, I have not reported to any official support providers.

[ray.wurlod]

You ought to.

[bkumar103]

We are using $PROJDEF to replace the parameter with the value from administrator. It is working fine. How did you know that it is not accepting the correct parameter.

[ray.wurlod]

You ought to.

[raji]

Kumar,

I am able to view the data when i give correct password. I have changed the password in admin like 'xxxx' (wrong password) and tried to view the data.

Naturally, it should give error like 'Security reasons. Password in valid".

But it is showing the data. thats why, i am saying its not taking password which i have changed in admin. I tried in another way also like giving wrong password first and then correct password. But it is not accepting.

[baglasumit21]

Hi,

In my project I am facing the following issue:

We developed datastage server (7.5.2) jobs in AIX environment(UNIX).

The jobs are running fine in Development environment. When we change the password(encrypted) in the administrator of same environment, its not reflected in the Job and its taking the old password.

But when we delete the parameter in the job properties for the password and again add the same parameter from the environment settings, it works fine.

If anyone has encountered any such kind of issues before, please help me out.

Thanks in advance

Have you compiled the jobs after changing the password value in administrator. Not sure Raji but you can give a try and see if it helps