CA PMO does not manage PDS/e datasets, then why are they listed in CA PMO displays?
CA PMO provides toleration support for LNKLST and private library concatenations containing PDSE data sets.
CA PMO is unable to manage PDSE-type libraries due to PDSE structural characteristics. CA PMO now has a DESERV parameter that, when set, installs a Directory Entry Services exit that captures GET calls to intercept and resolve directory searches when a PDSE library is in the LNKLST or private library concatenation.
Without QO80610, CA PMO will not manage any PDS's in a Private Library concatenation that are after a PDSE. When QO80610 is installed, CA PMO will manage the Private Libraries that follow a PDSE in a concatenation. But, CA PMO will still not manage the PDSE.
The D9 display lists candidate libraries in descending order by total number of searches. So the dataset is listed , because of the high number of searches.
However ultimately the library is marked as ineligible because it is a PDSE.