DSXchange

I'm having some problems with parameters.
I constructed some jobs with parameters and suddenly they do not work.

I created parameters for date source name, user and password, in DB2 stage.

And give me an error message saying that password or user is wrong.

If I take off the parameter and put fixed value, the job work.
When I make the the opposite (take off the fixed values and put the parameters) the job works.

But in some days, suddenly they do not work more and I have to do everything again.

Somebody already have this problem?

To clarify it follows the order of that it happens.

1 - the job(with parameter) aborted saying that password or user is wrong
2 - I take off the parameters and put fixed values
3 - run and execute the job(without parameter) - it work very well
4 - I take off the fixed values and put parameters
5 - run and execute the job (with parameter) - it work very well
6 - Some days, suddenly they do not work more and I have to do everything again.

Fernando Martins

Hi,
I had issues like this only when someone changed the job, never when it was untouched.
Are you sure no one touched the job?
the only other times it happend was when they actually changed the passwords.

Good Luck,

Nobody touched the job and nobody changed the password.

Fernando Martins

Hi,
then i think you should report this to your support provider

Did anyone go in and change the 'defaults' via the Director? This has been known to case the problem you are seeing, even if you don't touch the password field.

chulett wrote:Did anyone go in and change the 'defaults' via the Director? This has been known to case the problem you are seeing, even if you don't touch the password field.

Yeah, I've run into that one before. The defaults you save in Designer are one way, so everything looks fine in design time, but someone's changed them in Director (usually just the encrypted password field), so it fails to run with the bad login. It seems to me like changing the defaults in Designer only carries over to Director if a recompile is done. I may be wrong on that, but my experience with the default values leads me to that conclusion.

Nobody changed the 'defaults' via the Director.
The process was running every day and sunddely aborted.

Did the DB2 DBA change the password?

I've seen this problem on v6.0.1 too, but it's always been when someone changed a parameter value. I haven't seen it on v7.1.0 yet.

Good luck!

Tony

well, we did a restart in the Data Stage Server and the problem, not exist more.

somedoby knows of how much in how much time it is good for making a restart in the server?

Fernando Martins

It it's clean, less than a minute (measured from the time you press Enter on the command to start DataStage).

I think Fernando is asking how often the DataStage server should be restarted.

Possible. His English is still better than my non-existent Portuguese!

Theoretically, you should only need to restart DataStage on UNIX when you change something in dsenv or uvconfig, provided you let dsdlockd run. Of course, DataStage is restarted for an upgrade and if ever UNIX is rebooted.

Geez, Ray.

It it's clean, less than a minute

I think something is wrong in Denmark.

I've got one scheduled for tonight [my time] (after a change to dsenv). Will report back tomorrow.