On Wed, 28 Oct 2009 08:24:22 -0400, Andy White wrote: >We are debating within out department about doing dynamic changes with SET >PROG LNKLST and wanted to know how other shops might be handling it. We >are currently running z/OS 1.10 and we change the LNKLST on our lab >systems a few times in week leaving old LNKLST(s) sometimes out there. >Some of us though issue the UPDATE JOBNAME=* after which is my >understanding forces all jobs/stcs running to switch to the active one, >then delete the old ones . Then leaving one LNKLST on the system. We would >like to start to do this in production, less IPLS, smaller windows for >changes etc.
I would advise against this. I *have* used LNKLST UPDATE on production systems, but *only* as an alternate to an IPL when I had to get something important updated. It was always with the understanding that if something went wrong, an IPL might be required. IMO, it is asking for trouble to do it routinely. I have done LNKLST UPDATE on test systems many times and never had a problem. Still, I take the recommendation seriously. If you don't do the LNKLST UPDATE, the linklist that you used to IPL will remain active, but others may not. Many address spaces can be made to use the new linklist by recycling them. I also found that using descriptive names for the linklist helps a lot. You have 16 characters available. BTW, I am not convinced that any update of an in-use linklist is safe. IMO, creating a new linklist is safer. -- Tom Marchant ---------------------------------------------------------------------- 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
