Utility control statements

ARSEXOAM is controlled by utility control statements. The statements must appear one per line, with no line numbers. Control statements cannot be continued across lines. The statements consist of a single keyword-value pair. The table lists the keywords.
Table 1. Utility control statements (keywords) for the ARSEXOAM program
Keyword Use
ODINSTANCE Specifies the Content Manager OnDemand instance name for which objects are to be expired. This parameter is required and must specify an instance name in the ars.ini file and not a host name.
ODUSER Specifies the Content Manager OnDemand user ID to use for processing.
  • If unified login is enabled (that is, the ARS.PTGN dynamic exit has been enabled), the user ID returned by USS will be used; therefore the ODUSER can be omitted.
  • The user ID must have permission to delete objects from the application group.
ODUSERPW Specifies the password associated with ODUSER. Note: If unified login is enabled (that is, the ARS.PTGN dynamic exit has been enabled), a Passticket will be used; therefore, the ODUSERPW may be omitted.
COMMITCNT Specifies the number of fetches from the ARSOAM_DELETE, ARSOD, and ARSODIND tables that are to be done between COMMITS. If not specified, 1000 is used. If zero (0) is specified, no commits are done while fetching. The ARSOD and ARSODIND table are only processed if Content Manager OnDemand for OS/390 Version 2 migrated index rows are being deleted.
UNLOADMAX Specifies how many objects to hold in memory at any one time. The default is 100,000.
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.