Previous Topic: Configure CA Insight DPM for Use with CA Cross-Enterprise APMNext Topic: CA Insight DPM Post-Installation Recommendations


CA Insight DPM Installation Recommendations

  1. We recommend installing the optional history component. The history component lets you view past application and subsystem performance data, which is collected and stored in VSAM history files.
  2. If you install the history component, consider the following recommendations:
  3. We recommend not defining history files with a secondary extents specification. When the history file is initialized, CA Insight DPM initializes the entire file. This initialization causes the data set to extend into as many extents as possible. Use secondary extents only if you cannot allocate enough space in a primary allocation.
  4. Filter the history data (using the HISTORY-ACCT=FILTER SYSPARM option) when implementing history on systems that generate a high volume of accounting records. Filtering the records lets you specify which history records to keep in the history file for subsequent online viewing and which records to discard. Storing all records on a high-volume system can cause the data on the history file to wrap too quickly and generate an unnecessary CPU overhead. You can enable filtering in the HISTORY-ACCT SYSPARM option and customize the FILTERAC IQL request to generate a simple IQL WHERE clause that ignores unwanted records. We recommend using a WHERE clause similar to the following example:
    WHERE TOTAL-TIME-DB2 > .5
    

    This clause causes CA Insight DPM to store records that have an “in DB2”