My recollection is that when you zap a module, the module is updated in place in the load library. The module remains at the same location, so the pointer in the LNKLST is still correct. If the module is cached in VLF, then it takes a refresh to pick up the change. If the module is not cached in VLF but is a module that is read at start up by a subsystem or started task, then the subsystem may need to be restarted.
If you update a module with a linkedit or copy it from another library, then it is re-written and the library may go into extents. The new extent would not be known by LNKLST and you will get an 806 abend when the program is called. Depending on what is in the library, you may be able to compress and LLA refresh to get it back within the known extents (i.e. this can be dangerous to disastrous, it requires an in-depth knowledge of what is in the library and how it is used). We have replaced entire versions of products in production by building a new LNKLST, activating it, and making it the system default. There is a risk, but if you have a tired and true process to follow and have tested in a systems programmer test LPAR before hand, it can save IPL'es. We get maybe six IPL'es a year. Ken ---------------------------------------------------------------------- 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
