Peter, Thanks. That was much clearer than the manual.
Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Peter Relson > Sent: Wednesday, May 17, 2017 4:57 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: setrog lnklst question > > <snip> > and the LNKLST UPDATE JOB(*) is documented as potentially dangerous. > </snip> > > If you're lucky, nothing bad will happen. If you're really unlucky, you will > trash your system. And all sorts of variants in between. > The operation is unpredictably dangerous. The effects depend on what happens > to be going on at the time. > > If you use it, you will get no sympathy (or support) if something bad > happens. The only safe thing to do is not to use that option. > New jobs and new address spaces will use the newly activated LNKLST without > this option. > > You might check out the DELAY sub-option of LNKLST UPDATE. There is no way of > knowing how long might be necessary to delay before the system is to clean > up. And the command will not complete until the delay ends. > > Why is it provided at all? Because sometimes you're willing to take a risk if > your only choice is re-IPL. > > Peter Relson > z/OS Core Technology Design > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
