More important, has anyone actually experienced a problem with JOB(*)? . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com
-----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mark Zelden Sent: Wednesday, May 17, 2017 10:49 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: setrog lnklst question On Tue, 16 May 2017 23:10:10 +0000, Gibney, Dave <gib...@wsu.edu> wrote: >And the LNKLST UPDATE JOB(*) is documented as potentially dangerous. > >On the other hand, so far, I haven't have need to modify my linklst and >effect all running address spaces. It's usually limited to a smaller subset. Yet I continue to see people using it as a matter of habit instead of an "emergency" basis. The only place I have used it regularly is in a sysprog sandbox LPAR and since "delay" was added as an option, I use that along with it. LNKLST UPDATE JOB(*) DELAY(5) Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:m...@mzelden.com Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
