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
Number of columns in Transformer affects @INROWNUM
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
-
- Participant
- Posts: 197
- Joined: Mon Feb 17, 2003 11:20 pm
- Location: India
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: