How to: Activate PDS V2

Edit online

This topic describes how to activate PDS V2. By activating PDS V2, you can start using the latest version of persistent data store. After PDS V2 is activated for all components, PDS V1 is disabled.

Before you begin

Important: By default, PDS V2 is activated for the runtime environment, the monitoring server, and all monitoring agents. If you have not manually postponed PDS V2 activation for the runtime environment, monitoring server, or any of the monitoring agents, no additional action is required.

This task applies to environments where historical data is collected using the original persistent data store, PDS V1. Use this task if you have manually postponed PDS V2 activation for the runtime environment, monitoring server, or any of the monitoring agents.

Review the following important information before you attempt to activate PDS V2:

Review the content in PDS V2 activation.
If you have products in your environment that do not support PDS V2, do not attempt to activate PDS V2 for those products. You must continue to use PDS V1 for products that do not support PDS V2. For more information about products that support PDS V2, see PDS data set names and PDS V2 support.
When you switch 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 some data will be lost.
You must use PARMGEN or Configuration Manager to properly configure PDS V2; do not attempt to manually update your runtime environment settings to activate PDS V2. If you have manually configured any settings in your runtime environment prior to activating PDS V2, these settings will be lost when you refresh your runtime environment using PARMGEN or Configuration Manager.
Important: If you have manually updated any settings without using PARMGEN or Configuration Manager, it is recommended that you reconcile any discrepancies before continuing. If you are using PARMGEN, see Rectifying your PARMGEN configuration for more information.
If you are using PARMGEN, review the following scenarios:
- Scenario SMPE02: Applying SMP/E maintenance with configuration changes to an existing RTE and using IBM-supplied configuration defaults for new features
- Scenario SMPE03: Applying SMP/E maintenance with new configuration changes to an existing RTE and overriding the IBM-supplied configuration defaults
Note: If you are using PARMGEN as your configuration tool, consider migrating to Configuration Manager, which provides a simplified configuration process. For more information, see Introduction to Configuration Manager.
It is recommended that you review the appropriate topic:
- PDS V2 for the first-time OMEGAMON user
- Considerations when switching from PDS V1 to PDS V2

About this task

Activating the use of PDS V2 for historical collection is managed separately for the data collected on the monitoring server and data collected on monitoring agents. To use PDS V2 exclusively, PDS V2 must be activated for the runtime environment, all monitoring agents, and the monitoring server.

Although the use of PDS V2 is activated by default, activation for the runtime environment, the monitoring server, or one or more agents might have been postponed.

The following parameters control PDS V2 activation:

RTE_PDS2_ACTIVATION

Controls PDS V2 support for the runtime environment.

If RTE_PDS2_ACTIVATION is set to Y, PDS V2 support is enabled for the runtime environment. By default, the monitoring server and all monitoring agents are activated to use PDS V2. You can control PDS V2 activation for a specific agent using the Kpp_PDS2_ACTIVATION parameter, and you can control PDS V2 activation for the monitoring server using the KDS_PDS2_ACTIVATION parameter.

If RTE_PDS2_ACTIVATION is set to N, PDS V2 support is disabled for the runtime environment. In this case, parameters Kpp_PDS2_ACTIVATION and KDS_PDS2_ACTIVATION are ignored.

Kpp_PDS2_ACTIVATION

Controls PDS V2 activation for a specific agent.

Note: If PDS V2 is activated 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.

KDS_PDS2_ACTIVATION

Controls PDS V2 activation for the monitoring server.

Important: For PDS V2 to be activated for all components, all of these parameters (RTE_PDS2_ACTIVATION, Kpp_PDS2_ACTIVATION, and KDS_PDS2_ACTIVATION) must be set to Y. After PDS V2 is activated for all components, PDS V1 is disabled automatically, and the following message appears in RKLVLOG:

KPQS237I KPQHINIT: PDS V2 IS RUNNING STAND-ALONE, PDS V1 IS DISABLED

With PDS V1 disabled, PDS V1 data sets are no longer used and can optionally be deleted. For more information, see Removing PDS V1 data sets.

Use the following procedure to activate the use of PDS V2 for monitoring agents or the monitoring server. It is recommended that the monitoring server be the last component activated for PDS V2.

Procedure

Activate PDS V2 using one of the following methods:

Using Configuration Manager:
1. In RTEDEF(rte_name), add (or update, as appropriate) parameter RTE_PDS2_ACTIVATION, and set the value to Y. This will enable PDS V2 activation for the runtime environment.
2. If PDS V2 was previously deactivated for a supported monitoring agent, set the corresponding Kpp_PDS2_ACTIVATION value to Y in RTEDEF(Kpp$PARM) or RTEDEF(Kpp$lpar).
3. If PDS V2 was previously deactivated for the monitoring server, add parameter KDS_PDS2_ACTIVATION set to Y to RTEDEF(KDS$PARM) or RTEDEF(KDS$lpar).
4. Run the GENERATE action.
  The following messages appear in KCIPRINT and reflect the status of your PDS configuration:
```
KFJ00223I Global RTE PDS V1 setting is OFF
KFJ00224I Global RTE PDS V2 setting is ON
```
5. Start the monitoring server or monitoring agent.
Using PARMGEN:

Note: For details about performing each of the following steps, see Scenario SMPE03: Applying SMP/E maintenance with new configuration changes to an existing RTE and overriding the IBM-supplied configuration defaults.
1. Edit the configuration profile, as follows:
  1. From the Workflow - Primary Option Menu, select option 2, Customize PARMGEN configuration profiles.
    The Customize PARMGEN Configuration Profile Members (KCIP@PG6) panel is displayed.
  2. Select option 1 to edit the RTE profile.
  3. Set RTE_PDS2_ACTIVATION to Y, which will activate PDS V2 for the runtime environment.
  4. If PDS V2 was previously deactivated for a supported monitoring agent, set the corresponding Kpp_PDS2_ACTIVATION value to Y.
  5. If PDS V2 was previously deactivated for the monitoring server, add parameter KDS_PDS2_ACTIVATION set to Y.
  6. Save the changes and return to the Workflow - Primary Options Menu panel.
2. Regenerate the runtime members and jobs, as follows:
  1. Select Create the RTE members and jobs.
    The $PARSE/$PARSESV: Create the RTE Members and Jobs (KCIP@PR1) panel is displayed.
  2. Select option 1 to submit the $PARSE job (or the $PARSESV job, if variables are enabled).
  3. Return to the Workflow - Primary Options Menu panel.
3. Copy the runtime members from the work libraries to the production libraries, as follows:
  1. Select Submit batch jobs to complete PARMGEN setup from the menu.
    The Submit Batch Jobs To Complete PARMGEN Setup (KCIP@SUB) panel is displayed.
  2. Optional: Select option 11 and submit the KCIJPCPR job to back up the production libraries.
  3. Select option 12 and submit the KCIJPW2R job (or the KCIJPW1R job) to copy the work libraries to the production libraries.
4. Start the monitoring server or monitoring agent.

Results

If PDS V2 has been successfully activated for all components, PDS V1 is disabled automatically, and the following message appears in RKLVLOG:

KPQS237I KPQHINIT: PDS V2 IS RUNNING STAND-ALONE, PDS V1 IS DISABLED

With PDS V1 disabled, PDS V1 data sets are no longer used and can optionally be deleted. For more information, see Removing PDS V1 data sets.

Important: If you encounter problems when activating PDS V2 (such as receiving message KPQS235E), review your RKANPARU(KPQHINIT) member. If you have activated PDS V2 for all components, you should see the following settings:

PDSV1=OFF
PDSV2=ON

If this is not the case, it is possible that you are attempting to use PDS V2 for a product that does not support PDS V2, or there is some other incorrect configuration. If not all of your products support PDS V2, you must continue to use PDS V1 for products that do not support PDS V2. To correct the problem, do not attempt to manually update this member. Instead, make sure that all of your products support PDS V2, and then use PARMGEN or Configuration Manager to configure PDS V2 again. If this does not resolve the problem, contact IBM® Software Support.