You can use the auto-delete installation exit (CBRHADUX) to confirm or bypass automatic deletion of objects during an OSMC management cycle in your OAM system.
This installation exit executes as part of the OAM Storage Management Component (OSMC) mainline processing. OSMC can delete an object when its lifetime expires in accordance with the definition of the management class assigned to the object. An object can also expire through an explicit expiration date. If the object has an explicit expiration date, that takes precedence over the defined management class for the object. Before any object is deleted, OSMC calls the auto-delete installation exit to approve or deny the request for object deletion. This approval or disapproval for object deletion is dependent upon the return code returned by the installation exit. The installation exit also records the deletion of the object so that other applications are kept in synchronization with the OAM directory.
Exception: The installation exit is not called when a user requests deletion of an object during an OSREQ macro call.
OSMC performs the storage management cycle using a separate task for each storage group. The auto-delete installation exit can execute concurrently; therefore, it must be reentrant. A reentrant program is serially reusable. Each time the user enters the program, a fresh copy of working storage is provided. If any values must be saved, the user must save them in other storage areas or files.
The installation exit is called for every object that is to be deleted by OSMC and one last time when there are no more objects to delete. This last call does not include object deletion information.