I think I have another case for macro: skipping processed rows from a CSV file.
Suppose you have a CSV data set. In case you cannot use the same entry twice (e.g. the case deletes record in the database or whatever) you have to carefully trim the source CSV before each start to make sure it always stats from fresh entries. It would be great if JMeter's CSV dataset had "persist the number of processed rows" ability. That means, when a row is processed, JMeter updates a side file that notes the number of consumed rows. So, when next time the same test is run, JMeter picks up from where it left. Do you think JMeter core should handle the case? Do you think it is worth adding "persist the number of processed rows" (true/false/edit) property to "CSV Data Set Config"? Should the case better be handled by a macro "persistent CSV data set" that is a combination of a current CSV Data Set, and while loop that skips the rows? Vladimir
