How to: Postpone PDS V2 activation

Edit online

This topic describes how to disable PDS V2 activation. By disabling PDS V2 activation, you can postpone the use of PDS V2.

Before you begin

This task applies to environments where historical data is collected using the original persistent data store, PDS V1.

If you have products in your environment that do not support PDS V2, you must postpone PDS V2 activation for those products. For more information about products that support PDS V2, see PDS data set names and PDS V2 support.

Warning: 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.

It is recommended that you review the appropriate topic:

About this task

With the application of the PDS V2 maintenance, PDS V2 is enabled by default for the monitoring server and the monitoring agents.

If you want to opt out of PDS V2 activation until you are ready to use it, or if you have products that do not support PDS V2, you must disable PDS V2 activation for the monitoring server or the respective monitoring agents by performing the following procedure before starting the monitoring server or monitoring agent.

Warning: You must opt out of PDS V2 activation for the monitoring server or a monitoring agent before the initial startup of the monitoring server or monitoring agent. After switching to PDS V2, you cannot revert to PDS V1 without data loss.

You can postpone PDS V2 activation for the monitoring server, all agents in the runtime environment (RTE), or for specific agents only, allowing for an incremental rollout of PDS V2.

Note: It is recommended that the monitoring server be the last component activated for PDS V2.

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 activation 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.

KDS_PDS2_ACTIVATION

Controls PDS V2 activation for the monitoring server.

Important: For IBM OMEGAMON for Storage on z/OS, 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 for Storage users.

Procedure

Postpone PDS V2 activation for either of the following scenarios:

To postpone PDS V2 activation for the monitoring server and all agents in the runtime environment, disable PDS V2 globally for the runtime environment, as follows:
- Using Configuration Manager:
  1. Add RTE_PDS2_ACTIVATION N to RTEDEF(rte_name).
  2. Run the GENERATE action.
  3. 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 N.
    4. 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.
To postpone PDS V2 activation for the monitoring server or one or more specific agents, disable PDS V2 for the server or agent, as follows:
- Using Configuration Manager:
  1. Add RTE_PDS2_ACTIVATION Y to RTEDEF(rte_name).
  2. To postpone activation for the monitoring server, add KDS_PDS2_ACTIVATION N to RTEDEF(KDS$PARM) or RTEDEF(KDS$lpar).
  3. For each agent for which to postpone activation, add the corresponding Kpp_PDS2_ACTIVATION N to RTEDEF(Kpp$PARM) or RTEDEF(Kpp$lpar).
  4. Run the GENERATE action.
  5. Start the monitoring server or monitoring agent.
  The following messages appear in KCIPRINT and reflect the status of your PDS configuration:
```
KFJ00223I Global RTE PDS V1 setting is ON
KFJ00224I Global RTE PDS V2 setting is ON
```
- 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.
    4. To postpone activation for the monitoring server, add parameter KDS_PDS2_ACTIVATION set to N.
    5. For each agent for which to postpone activation, set the corresponding Kpp_PDS2_ACTIVATION value to N.
    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.