Diagnosing nondeletion/expiration of objects during OSMC processing

This information provides suggestions for handling the situation of objects not deleting or expiring during the OSMC processing cycle. This information allows you to identify, investigate, and overcome these problems.

If, during OSMC processing, objects that should have expired do not actually get deleted from the database, check if the auto-delete installation exit (CBRHADUX) is in SYS1.LINKLIB to be available to OAM to LOAD it when it starts. If the EXIT is not used, the OBJECTS will need to be deleted manually. One of the following situations is probably causing the problem:

The auto-delete installation exit (CBRHADUX) has been invoked and completed with a return code of either 0 or 8.
The object has not been selected for expiration processing by OSMC.

To diagnosis the problem, examine the system console log from the start of the OSMC processing of the storage group containing the object through the completion of the OSMC storage group processing. Look for any CBRxxxxx messages that might indicate a problem.

The CBRxxxxx messages are documented in z/OS MVS System Messages, Vol 4 (CBD-DMO).