text: The following parameters relate to the**ARSEXOAM**program: 
  
  (cid:2)**COMMITCNT**
  
  Specifies the number of fetches from the ARSOAM_DELETE, ARSOD, and ARSODIND 
  tables that are performed between COMMITS. 
  
  If this parameter is not specified, 1000 is used. If 0 is specified, no commits are performed 
  while fetching. The ARSOD and ARSODIND tables are processed only if Content 
  Manager OnDemand for OS/390 Version 2 migrated index rows are being deleted. 
  
  (cid:2)**UNLOADMAX**
  
  Specifies how many objects to hold in memory at any time. The default is 100,000. 
  
  (cid:2)**REQLIMIT**
  
  Specifies the maximum number of objects to send to the server in each request. This 
  number defaults to the**ARS_EXPIRE_REQLIMIT**parameter in the ars.cfg, or 100 if 
  **ARS_EXPIRE_REQLIMIT**is not specified. Load IDs for the same application group can be 
  grouped up to the**ARS_EXPIRE_REQLIMIT**value. All load IDs in a single expiration request 
  must belong to the same application group. For example, adding 
  ARS_EXPIRE_REQLIMIT=100 allows up to 100 load IDs for an application group to be 
  processed at a time. The optimum value to use is a function of multiple variables, including 
  table size. Suboptimal values might lead to table scans. EXPLAINs with various SQL that 
  uses the type of SQL that is involved help determine whether an index or a table scan 
  occurs. 