On Wed, 17 Jul 2019 09:28:57 -0500, Elardus Engelbrecht wrote: >I was also lucky, but when we do a LNKLST UPDATE, we rather do it after hours >if we simply cannot do a IPL.
If you simply cannot IPL, can you justify LNKLST UPDATE, knowing that it might cause you to have to IPL? I will admit that I have used LNKLST UPDATE, occasionally with JOB(*), but only when an IPL would have been tolerable. When creating a new LNKLST set, IMO you should consider carefully the reason for it and, if possible, recycle the address space(s) that you want to use the new LNKLST set. When you do an UPDATE of an address space, and all goes well, any new modules that are LOADed from LNKLST will come from the new LNKLST. However, modules that have already been LOADed from the old LNKLST set are still in memory, and you may end up with modules modules in that address space that are not compatible with each other. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
