>2) The library in question is defined with '0' (zero) secondary. >3) After the library was updated, an LLA REFRESH was done. >4) An LLA UPDATE was done (not sure if before or after the LLA REFRESH):
If the data set has no secondary extents, then none of the initial discussion was pertinent. It is necessary to do the LLA UPDATE/REFRESH so that LLA would have the updated copy of the directory entry that would locate the new copy of your module. Typically "refresh" is overkill, if you can instead use a more specific "update". Regardless, this is for getting the directory entry. LLA refresh will not help you in any way if the module is in a "new extent" of a LNKLST data set. That leaves open the possibility that you are encountering the error that I discussed. I can't think of any case where it is necessary (even appropriate) to do both an LLA UPDATE and an LLA REFRESH. >I didn't know that data sets already managed by LLA were refreshed I did not say that they were. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
