On Thu, 10 Jan 2013 10:15:56 -0800, Skip Robinson <[email protected]> wrote:
>If a shop has more than *one* sysprog, deferred LLA update/refresh is a >disaster lying in wait. YOU may think refresh will occur if and when YOU >are ready, but someone else may be navigating a different trajectory. >Depending on the module changes involved, premature refresh can cause >havoc. My rule is never to make any LNKLST library change that can not >tolerate an immediate refresh . > I have been at a lot of large shops including my current one and that is definitely true and I live by that same rule. However, I will will disagree with your "more than one" statement. In a small show with a few sysprogs, as long as everyone knows and plays by the same rules, it could work without a problem - and I've seen it work. Even in the large shop I am in now, everyone known never to do an LLA REFRESH except on a sysprog sandbox LPAR. Only LLA UPDATE. Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
