128 IBM Content Manager OnDemand Guide
Expiration Type
The Expiration Type determines how report data, indexes, and resources are expired. Three 
expiration types are available:
/SM590000Load: If the expiration type is Load, an input file at a time can be deleted from the 
application group. The latest date in the input data and the Life of Data and Indexes 
determines when Content Manager OnDemand deletes the data. Data that is stored in 
archive storage is deleted by the storage manager based on the archive expiration date. 
Load is the recommended expiration type.
/SM590000Segment: If the expiration type is Segment, a segment of data, which is a database file 
that contains index values for an application group, at a time is deleted from the 
application group. The segment must be closed and the expiration date of every record in 
the segment must be reached. If small amounts of data are loaded into the application 
group, and the maximum rows value is high, the segment might be open for a long period, 
and the data is not expired for the period.
/SM590000Document: If the expiration type is Document, a document at a time is deleted from the 
application group. Storing with an expiration type of Document causes the expiration 
process to search through every document in the segment to determine whether the 
expiration date was reached, resulting in long processing times.
Expiration Type Load is not allowed when you use the ARSLOAD ADD API or when you use 
the workstation APIs. If you plan to use these APIs with an application group, specify 
Document for the Expiration Type.
5.4.3  Advanced application group storage management
With the advanced storage management settings (Figure 5-25), you can adjust the size of the 
load object and determine when report data, indexes, and resources are migrated to archive 
storage.
Figure 5-25   Content Manager OnDemand for i Application Group Advanced Storage Management