Please find below, exec's that can be used in conjunction with PDSFLIST, to help you find modules/members easily within System/User library concatenations.

FL exec - Standard exec to invoke PDSFLIST. 

PROCLIB exec - This Rexx exec scans your JES2 procedure to determine which datasets are concatenated to PROC00. When used with an exec like DLIB, it can enable you to find procs quickly and easily.

LINKLST exec - This Rexx exec builds a list containing the names of all the datasets in the Linklist. When used with an exec like DLIB, it can enable you to find modules within the Linklist quickly and easily. Especially useful if you have a large Linklist and can never remember where modules are loaded from !

DLIB exec - Uses the above execs as decscribed. In addition it also contains code to scan your TSO dataset concatenations. This is useful to find ISPF modules/tables etc. The sample DLIB exec also has an example of a 'library group' structure. Datasets are logically grouped together by filetype and are scanned/displayed as such. This offers a much easier method of displaying and managing members from datasets that you 'view' as being of the same product/type etc. For example, you could set up a 'filetype' of libraries from a software product (source, tables, parmlib, loadlibs) and have all the details displayed in one list. In addition, you don't need to remember the MVS dataset names, the whole list is referenced by your 'filetype'.

SRCHFOR exec - Alternative to DLIB. Uses IDCAMS Listcat to obtain a list of requested datasets and then calls PDSFLIST (with an optional member list search list).

NOTE : If the Catalog Search Interface (CSI) is available (DFSMS/MVS 1.4 and above) then PDSFLIST will directly support specific DDNAME searches and Generic Filtered Lists of datasets.  The DLIB/LINKLST/SRCHFOR execs give examples of providing the same function without CSI.