text: **Content Manager OnDemand operation with the Tivoli Storage Manager**
  **server API**
  
  With the new event-based retention policy, the object expiration can now be event-based 
  instead of creation-based. A new option is available in the archive copygroup definition that is 
  called**RETINIT**. It determines the time when the retention time that is specified by the**RETVER**
  attribute is initiated. Two values are possible: 
  
  (cid:2) Creation: This value specifies that the retention time that is specified by the**RETVER**
  attribute is initiated at the time that an archive copy is stored on the Tivoli Storage 
  Manager server. 
  
  (cid:2) Event: This value specifies that the retention time that is specified in the**RETVER**parameter 
  is initiated at the time that a client application notifies the server of a retention-initiating 
  event for the archive copy. If you specify RETINIT=EVENT, you cannot also specify 
  RETVER=NOLIMIT. 
  
  We compare the behavior of Tivoli Storage Manager when Content Manager OnDemand data 
  is deleted with the previously listed two options together with the setting of data protection. 