Cataloging LNKLST data sets

Data sets in the LNKLST concatenation must be cataloged in either the system master catalog or in a user catalog.

Cataloged data sets must be defined using the standard search order for requests as outlined in z/OS DFSMS Managing Catalogsz/OS DFSMS Managing Catalogs. Variations in the standard search order can result in data sets not being found during LNKLST processing.

LNKLST data sets processed during IPL must be either cataloged in the master catalog or have their volume serials specified.

Note: The volume specification is not intended to get LNKLST to manage a data set that is not cataloged. It is designed to let the user put a user-cataloged data set in the LNKLST. Since user catalog support is not available when IPL is processing LNKLST, the volume must be specified to let LNKLST processing know where the data set resides. If a volume is specified, LNKLST processing will not try to locate the data set in the Master Catalog.

If you catalog a LNKLST data set in the system master catalog, the system will find the data set automatically during IPL.

If you plan to use a user catalog, you should be aware that the system will not find the data set unless you specify both the name of the data set and the volume serial number (VOLSER) of the DASD volume on which the data set resides. (This restriction also applies if you are defining the LNKLST concatenation in LNKLSTxx.)

Also, be aware that the system does not search OS CVOLs for LNKLST data sets.