PTF UJ92101 for APAR OA63966 (1Q23)

PTF UJ92101 for APAR OA63966 (1Q23) adds support for PDS V2 configuration for the Tivoli Enterprise Monitoring Server in the configuration software and modifies PDS V2 support for IBM OMEGAMON for Storage on z/OS.

Configuration Manager and PARMGEN updates

With this PTF, you can now configure the use of persistent data store V2 (PDS V2) for the monitoring server in both Configuration Manager and PARMGEN using the following parameters:

The default value for KDS_PDS2_ACTIVATION is N, so if it is not manually changed to Y, there is no functional change in the runtime environment.

If KDS_PDS2_ACTIVATION is set to Y and all agents in the runtime environment also have PDS V2 activated (which is the default setting), then PDS V1 is automatically disabled; PDS V1 modules will not be loaded and PDS V1 data sets are no longer allocated.

Configuration Manager action DELPDSV1, which is used to remove PDS V1 data sets after switching to PDS V2, has been updated with the names of the PDS V1 data sets for the monitoring server (RGENHISn, RppSGRPn, RPDSGRPn).

Product-specific updates

IBM OMEGAMON for Storage on z/OS

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

Configuration Manager and PARMGEN will no longer generate member &rhilev.RKANPARU(KDFDINIT), which contained the setting PDS2=FORC. This setting forced the IBM OMEGAMON for Storage version of PDS V2 to be used when the OMNIMON Base version of PDS V2 was disabled on a runtime environment level (by specifying RTE_PDS2_ACTIVATION to N). The PDS2=FORC option is no longer supported, and the IBM OMEGAMON for Storage agent will be moved to the OMNIMON Base version of PDS V2. History data sets cannot be reused.

It is important that the KDFDINIT member is removed from RKANPARU after applying this and related APARs. You must remove KDFDINIT from EXCLUDE rules and verify that is removed from RKANPARU.