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 ---------------------------------------------------------------------- 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
