232 IBM Content Manager OnDemand Guide
For example, when expiration processing starts on a specified server, you might see the 
following message:
“109 Cache Expiration (Date) (Min%) (Max%) (Server)”
Migration processing uses the specified date (the default is “today” in internal format). 
Expiration processing begins on each cache file system that exceeds the Max% (default 80%) 
and ends when the free space that is available in the file system falls below the Min% (default 
80%). 
One of these messages shows for each storage object that is deleted from cache storage. A 
storage object is eligible to be deleted when its “Cache Document Data for n Days” or “Life of 
Data” period passes (whichever occurs first). 
A storage deletion message looks similar to the following message:
“196 Cache Migration (ApplGrp) (ObjName) (Server)” 
Also, information-only messages report the percentage of space that is used in the file 
system.
An information message looks similar to the following message:
“124 Filesystem Statistics (filesystem) (% full)   (server)”
Load table (ARSLOAD)
The ARSLOAD table can be used to track loads for expiration. This table maintains a record 
of all successful loads to application groups with the “expire by load” expiration type.
10.5.3  Removing documents from the Tivoli Storage Manager archive 
Removing a document from archive storage means that the backup (if the primary document 
copy is in cache) or long-term copy (if the primary document copy is in archive) of the 
document is deleted from the system. Y ou remove documents from archive storage when you 
no longer have a business or legal requirement to keep them.
A management class contains an archive copy group that specifies the criteria that makes a 
document eligible for deletion. Documents become eligible for deletion under the following 
conditions:
/SM590000Administrators delete documents from client nodes 
/SM590000An archived document exceeds the time criteria in the archive copy group (how long 
archived copies are kept)
ASM does not delete information about expired documents from its database until expiration 
processing runs. Y ou can run expiration processing either automatically or manually by 
command. Ensure that expiration processing runs periodically to allow ASM to reuse storage 
pool space that is occupied by expired documents. 
When expiration processing runs, ASM deletes documents from its database. The storage 
space that these documents used to occupy then becomes reclaimable. For more 
information, see “Reclaiming space in storage pools” on page 233. 
Note: Y ou see one set of messages for each object server on which you run the ARSMAINT 
program.