Inaccurate dataset counts in Dataset Attribute Database workspaces

Context:

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

Issue:

After a VSAM dataset has been migrated, the cluster, data and index components are treated as individual datasets 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 dataset 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 dataset 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 datasets).