changes made are appearing in job are not appearing in seque

ranga1970 · Post by **ranga1970** » Sat Feb 05, 2005 4:44 pm

Hi,
I had created a server job, and i had mapped a field to a record, but later on it was found that that mapping is not correct and it was changed, this is brought through an hash file

but the problem, when i run this job individually, tha job brings correct records, but when a sequencer runs the job old field is brought

the hash file paths are different when we run jobs individually and sequentially and we use write differd in all hash files,
could some one suggest he possible cause

thanks
ranga

chulett · Post by **chulett** » Sat Feb 05, 2005 5:05 pm

Are your hash file direcotory paths supplied by job parameters? Are they being passed to the child job by the Sequencer?

ray.wurlod · Post by **ray.wurlod** » Sat Feb 05, 2005 6:07 pm

And are they being passed accurately?

Check the child job's log entries to view the parameter values with which its run was requested.

vmcburney · Post by **vmcburney** » Sun Feb 06, 2005 10:32 pm

Have you at some point copied and renamed your job? Perhaps your sequence job is pointing to an old copy of the job you are working on. Using DataStage Manager click on your job and choose the Usage Analysis option to see what sequence jobs are using it.

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Mon Feb 07, 2005 3:32 am

When your job sequencer runs, you can try to order the jobs by status in the DataStage director to check whether the job you expect to run are the ones that are really running.

Also you can see the job log's first few lines to check the parameters passed to it and its values to confirm the correctness of the flow.