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.
The debate starts because of the following disclaimer in the IBM manual (MVS SYSTEMS COMMANDS) we see the following disclaimer --------- SNIP ----- Be careful when you use UPDATE. Updating an address space while a program in that address space is fetching a module can cause the fetch to fail or to locate an incorrect copy of the module. The system does not attempt to verify the validity of the data for UPDATE. ---------------------- Questions 1) Does it hurt anything keeping the multiple lnklsts other than when you make changes it gets confusing, is there a memory constraint, or performance problem? 2) How many people out there issue on a production system the Update JOBNAME=* then delete the old LNKLST? have you had any problems? Thanks Andy The information contained in this message may be CONFIDENTIAL and is for the intended addressee only. Any unauthorized use, dissemination of the information, or copying of this message is prohibited. If you are not the intended addressee, please notify the sender immediately and delete this message. ---------------------------------------------------------------------- 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
