text: **Note:**You see one set of messages for each object server on which you run the**ARSMAINT**
  program. 
  
  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. 