text: **Turning on data retention protection**
  When you turn on data retention protection, the following descriptions explain what happens 
  when you use creation-based object expiration policy and event-based retention object 
  expiration policy: 
  
  (cid:2) Creation-based object expiration policy: Content Manager OnDemand issues no 
  
  commands to Tivoli Storage Manager. The objects are effectively orphaned by Content 
  Manager OnDemand and are expired by Tivoli Storage Manager based on their retention 
  parameters. If the retention parameters are set to NOLIMIT, the objects never expire. 
  
  (cid:2) Event-based retention object expiration policy: Content Manager OnDemand issues an 
  
  **event trigger**command through the Tivoli Storage Manager API. The event status of the 
  objects that are affected is changed from PENDING to STARTED, and the affected objects 
  are expired by Tivoli Storage Manager based on their retention parameters. If the retention 
  parameters are set to NOLIMIT, the objects never expire. 
  
  If a Content Manager OnDemand application group is deleted, a**delete filespace**
  command cannot be used with data retention protection; the operation is treated the same 
  as though a delete is indicated. The status of all of the affected objects is changed from 
  PENDING to STARTED, and the affected objects are expired by Tivoli Storage Manager 
  based on their retention parameters. This action leaves the file space entries in Tivoli 
  Storage Manager, so you must manually delete these entries when the file space is empty 
  (even with data retention protection on). 