Significance of generated CPP code in exported DSX file

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
visvacfirvin
Premium Member
Premium Member
Posts: 49
Joined: Fri Dec 14, 2007 1:43 pm

Significance of generated CPP code in exported DSX file

Post by visvacfirvin »

Hi,

I exported a DSX file to analyze CPP code in an exported DSX file. These are small codes that are generated in DSX file. I want to know the following details.

1. Significance of generated code. Does that really give exact logic of what is implemented in job?
2. I tried to check point no.1 using following steps.
a. Implement a simple lookup with condition and export DSX.
b. Remove the condition and export DSX.
c. Manually compare the DSX using Winmerge.
Now the first file has the logic for condition in an if loop.

Code: Select all

    if ((char_from_num(Sorted_Lnk.FLAG_IND) == InterVar0_0))
	{
		lookup(Lkup_Group0_1_Lnk);
	}
When i exported again after removing this condition, this logic in CPP code remained the same, whereas the logic in each DSRecord block was removed. If i change the logic, it was getting reflected. But if I remove the logic, CPP was not getting changed.
Is the generated CPP code just for reference ? What's the best way to look at the generated CPP code?

Thanks,
Firvin
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Determine your job number then look in RT_SCnnnn directory (a sub-directory in the project on the server) where nnnn is the job number.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
visvacfirvin
Premium Member
Premium Member
Posts: 49
Joined: Fri Dec 14, 2007 1:43 pm

Post by visvacfirvin »

OK. I'll Check there. But why it is different in the exported DSX?
Post Reply