Inaccurate data set counts in Dataset Attribute Database workspaces

Context:

VSAM data sets are typically reported under their cluster name in the Dataset Attribute Database workspaces. Although the data sets contain a cluster component, a data component and an index component, these components are counted as a single data set in the Dataset Attribute Database workspaces. In addition, only the cluster component name displays in the table views to represent the data set. In counters displaying the "Total Datasets" in a group, a single VSAM data set is counted only once.

Limitation:

After a VSAM data set has been migrated, the cluster, data and index components are treated as individual data sets by the Dataset Attribute Database workspaces. Each component appears on a separate line in table views. In counters displaying the "Total Datasets" in a group, each component is counted separately, increasing the data set count (in contrast to the count prior to migration).

Workaround:

No workaround is available. This discrepancy occurs because the catalog entry for a VSAM dataset is changed after the data set is migrated. The catalog entry change causes an inaccurate count. In fact, the Catalog Search Index reports these component names as type 'A' (Non-VSAM data sets).