text: (cid:2) For IBM i, depending on your retrieval patterns and system hardware configuration, it 
  
  might be advantageous to*not*store a duplicate set of documents in the Content Manager 
  OnDemand cache when you use ASM because ASM might already be using disk space. If 
  the application group uses ASM, caches the data, and specifies the migration of data at 
  load time, two copies of the data are stored during the load. One copy is stored in cache, 
  and one copy is stored in the ASMREQUEST directory. 
  
  To avoid storing a duplicate set of documents in cache for non-AFP data, change Cache 
  Data to No on the Storage Management tab of your application group definition. To avoid 
  storing a duplicate set of documents in cache for AFP data, you might change Document 
  Data to No Cache but leave Resource Data in cache for faster retrieval. 
  
  (cid:2) For IBM i, every user that loads data must have a home directory. If users do not have a 
  home directory, the temporary files are stored in the root directory of the integrated file 
  system (IFS). 
  
  (cid:2) If the data source is on a remote system, you can load the data into Content Manager 
  OnDemand on the remote system and directly store the export data to the specified 
  Content Manager OnDemand library and object server. 