Open Systems Features › Open Systems Menu › Maintenance Policy

Maintenance Policy

Use the Maintenance Policy dialog to manage the amount of data retained by the collector. CA SRM calculates an average for the data objects based on a time that you determine and keeps only this average value. For example, if you collect once a day, you can consolidate those daily values into a single weekly value.

You should try to schedule maintenance to run at times when users are not logged on and working, and when no collectors are running to retrieve data from the host. If a user has any type of window open for an object, or if a collector is retrieving data for that object, database maintenance for that object will be skipped (cannot be performed). Maintenance processing will, however, be performed on all the objects that are not currently in use.

To modify the policy, click the Modify button. This opens the Policy box. Select the amount of data you want combined into a single record. You can consolidate by:

• Minutes
• Hours
• Days
• Weeks
• Months

Select the amount of time you want left intact. This leaves the data in that time period out of the consolidation. For example, if you select to one week to remain intact, the policy consolidates all records together into a single average value except for the previous week. When you finish, click Save to save your changes. If you want to close the dialog without saving your changes, click Cancel.

When customizing a policy, use the following guidelines:

• Frequent file queries means more frequent maintenance
• A high number of records added in each execution means more frequent maintenance
• Frequent query execution means more frequent maintenance
• A low number of free disk space on the Application Server machine means more frequent maintenance

The policy consolidates data until the database reaches 0.5 GB. At this time, the database is split. The new database keeps the original database name. The old database receives a new name in the form of NN_(XXXX). NN represents the original database name and XXXX represents a sequential number. The first time the database splits XXXX is 0001. The next time a split occurs XXXX will be 0002 and so on. The Windows Client interprets the split databases as one and displays the information like it came from one source.

Note: There is one policy per Application Server.

Note: For information about scheduling of z/OS object trend logging Maintenance Policy, see the CA Vantage SRM User Guide.