How to: Change PDS V2 file count and file size

After you have been collecting and displaying historical data for a while, you might find it that you need to adjust the amount of data that you store. To change the amount of data, you adjust the number and size of files used by PDS V2.

Before you begin

Data written to the persistent data store is organized by tables (attribute groups) and data sets. The size of the persistent data store (spread across the data sets) and the activity of the system or subsystem monitored determines how much data is available. Initially, you should accept the default number of cylinders provided by each product (Kpp_PDS2_STORE_SIZE, Kpp_PDS2_SEC_SIZE). Eventually, you can determine the correct amount of space by observing the activity, as follows:
  • For space-based mode, how often the data set switch occurs.
  • For time-based mode, the usage of the primary extent if a secondary was not taken, or many secondary extents the data sets were taken.

Using this information, you can adjust the space accordingly. To help you make more specific calculations, the product documentation for the monitoring agents provides estimated space requirements or information about attribute tables. You might want to make your own calculations, based on site-specific factors: what types of monitoring agents are running, what resources are being monitored, how many resources, and so on. You can also take a trial-and-error approach. If you are not seeing as much data in your reports as you would like, you can override the defaults.

About this task

To increase or decrease the file count, edit the Kpp_PDS2_FILE_COUNT parameter. To change the size of the data sets, edit the Kpp_PDS_STORE_SIZE parameter (and optionally the Kpp_PDS2_SEC_SIZE parameter). The default value of Kpp_PDS2_FILE_COUNT is 6, with a range of permissible values from 2 to 36. The default value of Kpp_PDS_STORE_SIZE is different for different agents. (The Kpp_PDS2_SEC_SIZE parameter does not have a default value.)

The configuration changes will take effect after the monitoring server or monitoring agent is recycled. After the monitoring server or monitoring agent is recycled, it will allocate new PDS V2 data sets, if they do not exist, with the updated sizing specifications. If the PDS V2 data sets already exist, the monitoring server or monitoring agent will gradually make the updates, one by one (that is, one data set per each subsequent data set switch). Each time a data set switch occurs and a new reserved data set is allocated, the newly allocated data set will follow the new sizing specifications.

Procedure

Use either of the following methods:

  • Using PARMGEN:
    1. In the RTE configuration profile, edit any of the following parameters:
    2. Submit the $PARSE job to refresh the profile.
    Recycle the monitoring server or monitoring agent started task for the configuration changes to take effect.
  • Using Configuration Manager:
    1. In RTEDEF(Kpp$PARM) or RTEDEF(Kpp$lpar), update any of the following parameters:
    2. Run the GENERATE action.
    Recycle the monitoring server or monitoring agent started task for the configuration changes to take effect.