Description

The ARSMAINT program maintains application group data that is stored in the Content Manager OnDemand database and in cache storage. The ARSMAINT program maintains the system by using the storage management values from the application groups that are defined to the system. The ARSMAINT program uses the following storage management values:
  • Life of Data and Indexes
  • Length of Time to Cache Data on Magnetic
  • Length of Time Before Copying Cache to Archive Media
  • Length of Time Before Migrating Indexes to Archive Media
  • Length of Time to Maintain Imported Migrated Indexes
  • Expiration Type. The ARSMAINT program uses the Expiration Type to determine how to delete index data from an application group. The ARSMAINT program can expire a table of application group data at a time, an input file at a time, or individual documents.

Use the -d, -e, and -i parameters to migrate and expire index data from the database.

Use the -c and -m parameters to migrate and expire files from cache storage.

Note: Most maintenance processes should run when no other applications are updating the database or need exclusive access to the database and when you are sure that no one will be retrieving documents from the system. You should not maintain the database at the same time that you load data into the system. There can be other processes that conflict; for example, you cannot maintain the database while an offline backup of the database is in progress.

The time of day and frequency with which you run the maintenance programs and the processing options that you specify will vary, based on your requirements. For example, if you do not load data into the system every day or you add few rows to the database when you do load data, you should be able to maintain the database less often, perhaps once a month. However, if you load a high volume of data every day, you might need to maintain the database after the load processing completes. If your system has sufficient space available to store index and report data, you might be able to maintain the database less often.

The examples in this section illustrate one way to maintain the database and cache storage. You should use the examples as a guideline. The options that you use on your system and the times that you can run the ARSMAINT program on your system will be different.

ARSMAINT also queries the database for any application groups that are flagged for migration to an external storage manager, and creates migration links in the cache against which ARSMAINT is run. The migration date is the current date so when ARSMAINT normally processes files for migration, it picks up these newly created links.