Holds In OAM Are Not Recognized By CMOD

[Ed_Arnold]

If holds on data are placed in OAM, expiration processing could be an issue.

CMOD does not know about OAM holds.  Unpredictable results may occur including ending up with orphan data objects.

Any holds on CMOD data should be managed from CMOD itself.

The optional feature ERM (Enhanced Retention Management) is the supported solution for managing holds.

https://www.ibm.com/docs/en/cmofm/10.5.0?topic=ondemand-enhanced-retention-management-erm

Ed