job behaviour is diffrent

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
thumati.praveen
Participant
Posts: 106
Joined: Wed Oct 04, 2006 5:21 am

job behaviour is diffrent

Post by thumati.praveen »

Hi All,

I have one sequence and inside I am calling one job.
If I run the job through the sequence it is not working but I run individually it is working fine.

when I run through the sequence the lookups are not matching it is giving nulls because of nulls the transformer dropping the records.If I run the individul it matches the lookup and job runing fine.

what is the difference between these two methods runing?

Please give me the inputs if any one resolved the same problem before.

Thanks in Advance,
Praveen.
rajngt
Participant
Posts: 32
Joined: Wed Jan 04, 2006 6:22 am

Post by rajngt »

Are you passing the same parameters to the job when calling from the sequence?
bkumar103
Participant
Posts: 214
Joined: Wed Jul 25, 2007 2:29 am
Location: Chennai

Post by bkumar103 »

check the APT_STRING_PADCHAR parameter(Check if it is defined in the sequnce job). It might be set to default which is null. Change it to spaces.
Birendra
thumati.praveen
Participant
Posts: 106
Joined: Wed Oct 04, 2006 5:21 am

Post by thumati.praveen »

I was split the job then it is working fine.

Thnaks,
Praveen.
ag_ram
Premium Member
Premium Member
Posts: 524
Joined: Wed Feb 28, 2007 3:51 am

Post by ag_ram »

There should be NO difference, unless untill you specify Job Run Options(Limits, Warnings, General) while executing a Job through Designer or Director.
Post Reply