Remember - NGT Reorg does not actually HAVE a "logapply" phase. Whereas competing technologies need to scan the Db2 log during the latter stages of an online reorg, NGT Reorg is actually caching changes PAGES as the reorg progresses - these changed pages are then all that needs to be applied during the catchup part of the reorg. Of course, pages may still be changed while the catchup is proceeding - hence the need for an iterative cycle of catchups until all is done
As such it makes no sense in the context of Unloading data
Hope this helps
Thanks Phil for the clearification.