On Fri, 10 Nov 2006 08:01:31 -0500, Peter Relson <[EMAIL PROTECTED]> wrote:
>No, there is no safe way to expand SYS1.LINKLIB on the running system. > >If you want an unsafe way, >- create a copy of SYS1.LINKLIB such as SYS1.LINKLIB.COPY >- create a LNKLST set that specifies NOCHECK and includes SYS1.LINKLIB.COPY >in the right place along with specifying SYS1.MIGLIB and SYS1.CSSLIB in the >right places (and if you're on z/OS 1.8, SYS1.SIEALNKE and SYS1.SIEAMIGE). >- activate that LNKLST set >- get all users off of the old LNKLST. This is unpredictably dangerous >(ranging from harmless to fatal), such as by SETPROG LNKLST UPDATE JOB(*). >Now no in-use LNKLST has SYS1.LINKLIB. >- get LLA to stop using SYS1.LINKLIB. A REMOVE statement in CSVLLAxx might >do it. Or you might have to purge LLA. >- Now there is no one using SYS1.LINKLIB and the system's ENQs on >SYS1.LINKLIB will be released. >- Now you can do whatever you want with SYS1.LINKLIB. >- And then if you're equally adventurous you can repeat this process doing >the analogous stuff to get rid of SYS1.LINKLIB.COPY and restore use of >SYS1.LINKLIB. > >Peter Relson >z/OS Core Technology Design > How heavily used is this ADCD system? While most if not all will tell you not to attempt this on a live system, I have contracted at several very small environments using an ADCD system that didn't have anything set up for cloning new sysres volumes, indirect cataloging etc. and have used the unsafe method outlined above. You are probably in the same boat, so I'm sure you don't want to go through all the trouble of setting up a cloned system for 1 PTF. Perhaps you don't have the expertise even to do that. Another option - which is safe - is to create the copy of SYS1.LINKLIB and specify it in PROGxx as SYSLIB LINKLIB(SYS1.LINKLIB.COPY) and IPL. Then apply your PTF to SYS1.LINKLIB (I don't think your OP said it had to be applied "to the running system"). Then you can remove the SYSLIB or replace the specification with an empty "dummy" library and re-ipl with SYS1.LINKLIB. If you decide to leave in SYSLIB LINKLIB(dsn), make sure you specifically add SYS1.LINKLIB to the LNKLST set. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - GITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
