The IBM Tivoli Monitoring on z/OS framework and OMEGAMON now supports persistent data store V2 (PDS V2) for all history data sets. You can now use extended address volumes (EAV) for all history data sets and all OMEGAMON datasets.
Before this PDS V2 is used by all OMEGAMONs for near team history collection but PDS V1 was still required for writing History data to the Tivoli Data Warehouse (TDW) and recording near team history attributes at the TEMS. And PDS V1 files can not be allocated on large EAV volumes
Using Configuration Manager or PARMGEN, you can now configure the use of PDS V2 instead of PDS V1 for the Tivoli Enterprise Monitoring Server using the new KDS_PDS2_* parameters. APARs OA63242, OA63770, OA63966 now provide this support with PTFs UJ92100, UJ92097 and UJ92101. These IF-REQ each other so all will be needed to be installed at the same time. When installed there will be no change to how HISTORY is collected and you will have to activate PDS V2 in place of PDS V1 when you are ready.
Example of RKLVLOG Messages:
13:57:29.19 KPQD0102I KPQHINIT: KPQHINIT INPUT PARAMETER: PDSV1=OFF
13:57:29.19 KPQD0102I KPQHINIT: KPQHINIT INPUT PARAMETER: PDSV2=ON
More information can be found in OMEGAMON Shared Documentation:
OMEGAMON Shared Documentation (ibm.com)