Implications of del large filespace

Hi

I am running TSM 6.3.4.2 on AIX. DB size is 100Gb, we don't do any dedup.

I have one AIX node that had a filespace with 31 million files in. This data was then moved to a new filesystem on the AIX client and hence was backed up again under a new filespace. Obviously this has resulted a nice increase in TSM database size.

I'm now in a position where I can delete the old original filespace with 31 million files in. I wondered if there are any gotcha's to look out for when I do this in terms of active/archive log space, other than making sure I don't run out, and also around database reorgs.

Currently we have set
ALLOWREORGTABLE Yes ALLOWREORGINDEX No
REORGBEGINTIME 06:00 REORGDURATION 24

Am I likely to see the database size reduce in the weeks following the deletion of this filespace once table reorg has had a chance to do its thing?
Under what circumstances should I enable reorgindex ?

Many Thanks