I know nothing about ISPCFIGU but if you say it works when ISPLLIB then you should consider that that is where it needs to go.
It is fully possible that an application searches only a specific DD for a module. Being in the LNKLST works if that is the first thing searched. I'd guess that ISPF searches ISPLLIB first. If what it is looking for is found via ISPLLIB then that's the copy that's going to be used. And I have no idea what it does if the module is not found in ISPLLIB. Does it give up? Does it do a "normal" fetch? If you "pull the module from LNKLST" (I do not know what that means, but I'll guess you mean that you "load" it or do some other "module fetch" operation) then in 100% of cases of "module fetch" the defined system search sequence will be followed. If you want to eliminate LLA from possibly picking up a cached copy of the directory entry, yes, an update or refresh will work, but you could, if you were playing, simply stop LLA. On your production system you might not want to stop LLA because of the negative performance ramifications. 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
