Considerations when switching from PDS V1 to PDS V2

Review these considerations when switching from PDS V1 to PDS V2.

Minimize data loss

Warning: When you switch to from PDS V1 to PDS V2, near-term historical data that is in your PDS V1 is not migrated to PDS V2. It is possible that a day or two of data will be lost.

When you switch to from PDS V1 to PDS V2, near-term historical data that is in your PDS V1 is not migrated to PDS V2. It is possible that a day or two of data will be lost. Because of this, consider the timing of your switch to PDS V2. For example, you could plan to switch to PDS V2 over the weekend so that your near-term data is available on Monday for the week.

Initial configuration settings

With the application of the latest PDS V2 maintenance, PDS V2 is activated by default for the runtime environment, the monitoring server, and the monitoring agents. Unless manual steps are taken to postpone PDS V2 activation, all components will switch to PDS V2 when the runtime environment is refreshed.

The initial PDS V2 parameter values are taken from PDS V1 settings in your configuration, so you might want to review them:

RTE_PDS2_HILEV: If the value for this parameter does not match your current PDS V2 high-level qualifier, you will not be able to see old data and old data sets will no longer be used.
Kpp_PDS2_FILE_COUNT: Adjust the value of this parameter to use 8 (eight); otherwise, the historical data storage capacity will be different from the one currently used.
Kpp_PDS2_STORE_SIZE: Adjust this value according to your current settings, otherwise historical data storage capacity will be different from the current one.

If you want to make customizations, you need to change the PDS V2 parameters, as any change to PDS V1 parameters will not be honored after switching to PDS V2. If you need to customize PDS V2 parameters in Configuration Manager, you will need to add these parameters with the required values to the following members:

For the monitoring agents: RTEDEF(Kpp$PARM) or RTEDEF(Kpp$lpar)
For the monitoring server: RTEDEF(KDS$PARM) or RTEDEF(KDS$lpar)

Products that had two PDS V1 data stores will only have one consolidated PDS V2 data store with a size equal to the sum of the existing PDS V1 data stores (for example, KM5, KS3/KDF).

For more information about PDS V2 parameters, see PDS V2 parameters and members.

Phased rollout

To do an incremental PDS V2 rollout, you would leave RTE_PDS2_ACTIVATION set to Y but set Kpp_PDS2_ACTIVATION to Y only for the specific agents you want to switch to PDS V2. For the agents that should remain using PDS V1, set the corresponding Kpp_PDS2_ACTIVATION parameter value to N.

PDS V2 for the monitoring server is also activated by default. It is recommended that the monitoring server be the last component switched to PDS V2. You can control PDS V2 activation for the monitoring server using the parameter KDS_PDS2_ACTIVATION.

Important: For IBM Z® OMEGAMON® AI for Storage, you cannot postpone PDS V2 activation. You must switch to the latest OMNIMON Base version of PDS V2. For more information, see Considerations for OMEGAMON AI for Storage users.

If PDS V2 is enabled for an agent, the PDS V1 data sets will not be allocated by default in the Configuration Manager GENERATE action or the respective PARMGEN allocation jobs.

Considerations for OMEGAMON AI for Storage users

For IBM Z OMEGAMON AI for Storage, the IBM Z OMEGAMON AI for Storage internal version of PDS V2 and the use of PDS V1 are no longer available. IBM Z OMEGAMON AI for Storage users must use the OMNIMON Base version of PDS V2.

After switching to PDS V2

If you want to customize PDS V2, you need to change the PDS V2 parameters, as any PDS V1 parameters will not be honored after switching to PDS V2 (that is, the first Configuration Manager GENERATE run after the PTF installation or the first refresh of the PARMGEN work environment).
After successfully switching to PDS V2 (including the monitoring server), you can remove all PDS V1 data sets. For more information, see Removing PDS V1 data sets.
Note: After successfully switching to PDS V2, the PDS V1 data sets will no longer be allocated by the Configuration Manager GENERATE action or in the respective PARMGEN allocation jobs.