Originally posted by: malag

1)Is there anyway to control the number of times a map has to be executed.
2)how can we stop the map after reading 100 records?
Thanks in advance
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: SPG

On the input side create a group which has the following elements:
Record(1:100)
Blob(0:s)

Then in your map, have a functional map where you pass the "Record".

I am not aware of any starightforward "For" loop in TX.
SPG
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: SystemAdmin

For 1, you can call the map from other map using if condition, if INDEX() <= CertainNumber, call map otherwise none
For 2, you can call functionalmap, if INDEX($)<=100

Let me know if this logic can able to solve your problem, setting range for Record in type tree in one option but there is lesss flexibilty in that option, component rule in map is easy to change.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Hi,

A good way to simulate a loop with TX would be to call a functional map giving as parameters :

• your specific data necessary for your processing,
• a CLONE of an item and the number of executions

eg :F_FunctionalMap (CLONE(+Item+,+Number of executions+),MyData)

Doing so your functional map will exactly be called as many times you specified.

You may add the INDEX() value as parameter of the functional map to make it aware of present execution occurence.

Reg.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: TarunB

Simply -

1) Control the source trigger to only produce 100 trigger files/messages. Or use a pre-processing map that keeps a count of how many triggers you have received.

2) Use a FetchUnit of 100 in your input card, keeping FetchAs value of Integral. This will process only the first 100 records. The assumption is that your input structure is defined so as to easily define each record.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender