You may need to enable the SYMAPI_TF_COUNT_MODIFIED_TRACKS parameter in the options file to see the deltas in the query output.

Thanks Jasonc.

Yes all the time I see modified tracks count sticks to 0. I will check for a document which gives more info on enabling the option.

2nd question: once activated and 100% copied source and target are independent devices with their own data. So modifying the tracks on both source and target and increase in the count of modifying tracks will it occupy more space on cache or where this tracking info will be stored. Will it have any impact on performance by any chance?

There is no additional overhead in monitoring the modified tracks or additional cache required after the copy is complete, nor performance overhead. As you say, they are effectively independent devices (copy on first write is no longer going to occur).

The (replication) cache allocation is done at the point that the source <> target relationship is created. It is returned after the terminate completes.

Thanks a lot.