Improve IMS catalog retention criteria / IMS catalog record purge utility

Currently there is no way to clean up the IMS catalog with the IMS catalog record purge utility without having a risk to loose an active catalog instance, because you can only specify IMS catalog retention criteria in the IMS PROCLIB DFSDFxxx member based on either a number of instances which should be kept or based on the age an instance at least must have before it is being removed from the IMS catalog. In both cases you either have to specify very high values, which would mean that nothing is being cleaned up and IMS catalog performance is becoming worse and worse (and more and more disk space is being used) or you are risking to loose your active or maybe even also the staging catalog instance of a DBD or PSB.

With IMS managed ACBs the IMS catalog stores the timestamp of both active and staging instance in a DBD or PSB record. Without having DB versioning activated during the clean up every other instance could be removed from the IMS Catalog without having a risk to loose a instance which is still being needed. Please enhance IMS catalog record purge utility to be able to do such a clean up either based on input statements or based on a new retention criteria. Please also consider that in the case DB versioning is active it might be necessary to keep more catalog instances. Please create a solution for this problem which also can be used in the case DB versioning is actively used.