test connection failed in a datastage job using DB2connector

[peep]

Hi All,

I am running a sample datastage job.

using DB2 connector stage and peek

When I run the job it is successfully finished.
when I open the db2 connector stage and test connection I get an error username/password invalid .
"security processing failed with reason24 USER NAME/OR PASSWORD INVALID sqlstate =08001
TEST 1:
so I gave a wrong user id in parameters and compiled and ran the job.
Then job failed with an an error username/password invalid .

Any suggestion ?
did any one experienced this ?

[ray.wurlod]

Use a correct username/password.

Make sure that the username/password has not expired.

[peep]

I tried to connect to the database via unix and it connected.

db2 connect to database xxxxxx user xxxxx
password xxxxx

and it connected.

[peep]

Any thoughts /suggestions?

[PaulVL]

Type them in again.
Look at the job log for those parameters. Perhaps you are not using the user id you desired...

You might have over written it at a job level rather than using the one passed by your sequencer. Got $PROJDEF?

Instead of doing a test connection, try running the job with the db2 stage as your read, and a peek as your target. See what the job log spits out as your user id.

[peep]

I did created a new job ,new parameter sets and tried test connection and it failed.

But job ran successfully.

I suspect that something needs to be done with cataloging.

When the DBA cataloged database with alias name the job ran successfully and test connection passed.

When cataloged with actual database name then test connection failed but job passed.

[peep]

Type them in again.
Look at the job log for those parameters. Perhaps you are not using the user id you desired...

yup , I looked at the job log and it has all correct(desired entires).