>the LNKLST does not like identically named datasets on different volumes
I'd say it is stronger than "does not like". One of the reasons is LLA which does not deal with uncataloged data sets yet wants to deal with the LNKLST. Something like this has happened: -- The system IPLed with data set X in the LNKLST which was either located in the master catalog or its volume was provided -- Later in IPL, "normal" allocations are done for data set X (using the current catalog). That allocation found that according to the catalog X is not where the system found it during IPL. This inconsistency means that LLA (and quite possibly other things) will not work. That is what the message is trying to tell you. -- Probably, when there was a LNKLST DEFINE with COPYFROM from the IPL-time LNKLST set, or from a LNKLST set that itself was copied from the IPL-time LNKLST set, the system copied everything (including that original volume definition). And then the allocation found the new catalog entry, resulting in"no match". Again, the message tells you that. --You could try defing the LNKLST set from scratch, without copyfrom (aside from the system-defined data sets). That will be a pain, of course, but the OP does not seem willing to re-IPL although by now that would probably have saved a lot of time. By not using COPYFROM (or perhaps by using COPYFROM but then deleting specific data sets and then re-adding) there would be no IPL-time data in play. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
