Number of columns in Transformer affects @INROWNUM

sumitgulati · Post by **sumitgulati** » Fri Mar 04, 2005 1:21 pm

Hi,

I have a job in which I use system variable @INROWNUM. It is a simple job with two transformers. In the first transformer I make a lookup to a hash file which is right now empty and hence does not return any records.

The @INROWNUM is not behaving as expected. It starts with 2 instead of 1 and when I run the job for 100 records we also noticed that the @INROWNUM value is 100 for two records. After spending some time with the job we found that it seems to be a problem associated with the number of columns in the first transformer stage. Upto 95 columns the job works fine but when we add 96th column the @INROWNUM starts to begin with 2.

Does any one know why is this happening.

Thanks and Regards,
-Sumit

Mike · Post by **Mike** » Fri Mar 04, 2005 2:05 pm

Do you have row buffering enabled for active-to-active links? If yes, try turning it off.

Mike

sumitgulati · Post by **sumitgulati** » Fri Mar 04, 2005 3:12 pm

Thanks a lot Mike. It worked.

Regards,
-Sumit

ray.wurlod · Post by **ray.wurlod** » Sat Mar 05, 2005 10:18 pm

You can also get this behaviour if the source file is accessed through a Sequential File stage with the "first line is column headers" property set.