I am seeing this problem where we have an MDC table organized by time
dimension id.

There are currently 1301 total rows within the table, and 350 distinct
time ids avg'ing out to 3.8 rows per time id.

We run an mdc_blk check with the SQL below:

select          substr(tabschema,1,20) as tabschema                  ,
                    substr(tabname,1,30) as tabname
   ,
                     card                             ,
                     npages                       ,
                     fpages                       ,
                     clustered         ,
                    active_blocks        ,
                    substr(index_tbspace,1,20) as index_tbspace  ,
                    substr(tbspace,1,20) as tbspace
from syscat.tables
where tbspace = '<tbl_space>'
    and clustered = 'Y'
order by 4,5

Back to this table: there are

CARDS = 1301 CARDS
NPAGES =  350
FPAGES = 22464

So from this information, 1301 rows are taking up to 22,000 32K pages,
which is roughly 700MB worth of storage.

Does this sound reasonable?  Can someone explain to why this is
happening?