How to: Change PDS V2 file count, size, and location

Edit online

After you have been collecting and displaying historical data for a while, you might find 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. You can also change the volume where the data sets are allocated.

Before you begin

Initially, you should accept the default number of cylinders (or megabytes) 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 extent is not taken) or how many secondary extents are taken for the data sets.

Using this information, you can adjust the space accordingly.

Note: This task describes how to modify the data sets for the monitoring agents using Kpp_PDS2_* parameters. You can also make these changes for the runtime environment (using RTE_PDS2_* parameters) and for the monitoring server (using KDS_PDS2_*) parameters.

About this task

You can modify persistent data store data sets as follows:

To increase or decrease the file count, edit the Kpp_PDS2_FILE_COUNT parameter. The default value of Kpp_PDS2_FILE_COUNT is 6, with a range of permissible values from 2 to 36.
To change the size of the data sets, edit the Kpp_PDS2_STORE_SIZE parameter (and optionally the Kpp_PDS2_SEC_SIZE parameter). The default value of Kpp_PDS2_STORE_SIZE is different for different agents. (The Kpp_PDS2_SEC_SIZE parameter does not have a default value.)
To change the volume where the data sets are allocated, edit the Kpp_PDS2_VOLUME parameter. If a value is not specified, parameter Kpp_PDS2_VOLUME uses the value from parameter RTE_PDS2_VOLUME.
Note: When allocating data sets, PDS V2 passes the Kpp_PDS2_VOLUME parameter value as the VOLUMES parameter in the z/OS IDCAMS utility DEFINE CLUSTER command. For SMS-managed data sets, the volume specified might not be used. For more information, see SMS volume selection for data set allocation.

The configuration changes take effect after the monitoring server or monitoring agent is recycled. After the monitoring server or monitoring agent is recycled, it allocates new PDS V2 data sets if they do not exist, with the updated sizing and volume specifications. If the PDS V2 data sets 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 and volume specifications.

Procedure

Use either of the following methods:

Using PARMGEN:
1. In the RTE configuration profile, edit any of the following parameters:
  - Kpp_PDS2_FILE_COUNT to specify the number of files
  - Kpp_PDS2_STORE_SIZE to change the primary allocation size of each file
  - Kpp_PDS2_SEC_SIZE to change the secondary allocation size of each file
  - Kpp_PDS2_VOLUME to change the volume where the data sets are allocated
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:
  - Kpp_PDS2_FILE_COUNT to specify the number of files
  - Kpp_PDS2_STORE_SIZE to change the primary allocation size of each file
  - Kpp_PDS2_SEC_SIZE to change the secondary allocation size of each file
  - Kpp_PDS2_VOLUME to change the volume where the data sets are allocated
2. Run the GENERATE action.
Recycle the monitoring server or monitoring agent started task for the configuration changes to take effect.