How CA PMO Optimizes Directory Searches › Searches Initiated by a Program or Application › How CA PMO Optimizes Program-initiated Searches › Directory Searches of Private Librariess Only (Optimized by CA PMO)

Directory Searches of Private Librariess Only (Optimized by CA PMO)

If a program issues a BLDL/FIND request to initiate a directory search, the request could be resolved by an in-storage search if LLA is managing the libraries in the concatenation. However, at this point CA PMO gains control, and it searches the hash tables for the member.

1. If CA PMO finds the directory entry for the member in one of the hash tables, the search ends successfully from the hash table. DASD I/O is eliminated because the member is located from CA PMO in-storage search.
2. If CA PMO does not find the directory entry for the member in the hash tables, the search ends unsuccessfully. DASD I/O is eliminated because CA PMO in-storage search determines that the member cannot be found.

For all private libraries that CA PMO manages, the DASD searches shown in the illustration titled Private Libraries Only Search are replaced with in-storage searches of the CA PMO software cache.