While reading a DB2 tech report and best practice , I see that many IBM DB2 internal experts now do not suggest running reorgchk to find out the tables that needs to be reorg’d .  Instead they suggest using the following sqls to find the tables that needs to be reorg’d :

select TABNAME
from SYSIBMADM.SNAPTAB
where (ROWS_READ > 999)
and ((OVERFLOW_ACCESSES * 100) / (ROWS_READ + 1) > 3);

One of the primary reason is that they want to avoid running runstats before the reorgchk.  While this can find the tables that needs to be reorg’d, it doesn’t help to find the indexes. The only way to find the indexes are still via reorgchk.
I am currently testing this and incorporating this to my offline reorg script and inplace reorg