text: **General**
  Consider the following general recommendations when you work with OAM for Content 
  Manager OnDemand: 
  
  (cid:2) Define a user catalog exclusively for collection names. 
  
  (cid:2) Cache the user catalog in the virtual lookaside facility (VLF). 
  
  (cid:2) Migrate objects to optical or tape (OSMC) during non-peak hours. 
  
  (cid:2) Spread OAM collections over multiple DB2/disk/channels. 
  
  (cid:2) Spread out the application groups to different collection names: 
  
  OAM collections → storage groups → DB2 database 
  
  (cid:2) Group your applications based on retrieval expectations: 
  
  – Collect small, frequently used applications together. 
  – Isolate your important applications so that the other applications do not get in the way. 
  
  **DB2**
  Consider the following list of recommendations that relate to DB2: 
  
  (cid:2) Ensure that enough DB2 connections are available to support the OAM requests. 
  (cid:2) Run the**REORG**,**RUNSTATS**, and**REBIND**commands, as appropriate. 
  (cid:2) Partition OAM table spaces larger than 2 GB. 
  
  **Devices**
  Consider the following recommendations that relate to devices: 
  
  (cid:2) Determine and set the Initial Access Response Seconds (IARS) option. 
  
  (cid:2) Assign objects to storage classes that have an adequate IARS that is defined and to 
  management classes that do not cause a transition to a slower storage class until the 
  frequency of retrieving the objects is reasonably low. 
  
  (cid:2) Determine whether to place the object on disk or removable (optical or tape) media. 
  
  (cid:2) If the IARS opts for REMOVABLE media, determine whether to place the object on optical 
  or tape. 
  
  (cid:2) Verify that the required Sustained Data Rate is achieved based on the selected object 
  placement. 