Hi. Sorry I'm late to the game here.
Pankaj is right on both counts about cache expiration -- historically, cache expiration was set at load time -- to make maintenance fast and easy by simply deleting directories that contained data that should have expired. Of course, CPU power and IO bandwidth have improved dramatically, making this method obsolete. Today, and for a few years now, CMOD has been inspecting the contents of the cache and determining what is due to be expired based on the CURRENT cache expiration settings in the OnDemand Client.
The same applies for DB2 index expiration. When configured properly, CMOD will expire records based on the CURRENT settings of the Life Of Data And Indexes parameter.
Maybe we should make a guide of FAQ for this topic.
Does anyone else have any questions (or information to share?) about extending retention?
-JD.