PDS V2 is enabled for application application-name. PDS V1
near-term history files exist for this application, but PDS V2 files do not exist yet. This
situation normally triggers the migration process of PDS V1 files to PDS V2. However, the monitoring
server or monitoring agent is configured with PDS V1 disabled, so the PDS V1 environment is not
initialized, and the migration cannot be performed.
System action
The PDS migration process for the application will not be performed. Empty PDS V2
application files will be created, but the application data from PDS V1 will not be migrated.
History data collection for the application will begin in PDS V2. If the
application-name in the message is KPD, Tivoli Data Warehouse
(TDW) export configuration data stored in PDS V1 will be lost, which may cause a spike in CPU usage
the next time history data is exported to TDW.