Chapter 10. Migration and expiring data and indexes 237
The following parameters relate to the ARSEXOAM program:
/SM590000COMMITCNT 
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.
/SM590000UNLOADMAX 
Specifies how many objects to hold in memory at any time. The default is 100,000.
/SM590000REQLIMIT 
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.
ARSEXPIR
The ARSEXPIR program can be used to process System Management Facility (SMF) records 
that indicate that Content Manager OnDemand objects expired and to remove the associated 
index entries for those objects.
Figure 10-5 on page 238 illustrates two methods that the ARSEXPIR program uses to expire 
OAM and VSAM objects.
Notes: 
/SM590000If one object for a load ID is deleted, all of the index entries for that load ID are deleted.
/SM590000Index entries of all OAM objects that are recorded as being deleted by rows in the 
ARSOAM_DELETE table are deleted regardless of the settings in the Life of Data and 
Indexes section on the Storage Management tab of the application group. 
/SM590000If you plan to use Storage Management expiration, ensure that you set the expiration 
type of all application groups to Storage Manager.
/SM590000The recommended expiration type for Content Manager OnDemand is Load. Content 
Manager OnDemand supports the expiration type of Load with the use of ARSEXOAM for 
expiring the indexes in Content Manager OnDemand. 
/SM590000Storage Manager expiration is incompatible with Enhanced Retention Manager and 
Content Federation Services for Content Manager OnDemand.