The easiest method to compress a library for maintenance runs is to use the SMP/E option COMPRESS(xxxxxx), or COMPRESS(ALL), where xxxxxx is the name of the specific library(ies) to compress. SMP/E will delete all the modules which are to be changed, then compress the library, then apply the maintenance.
But there is no subsitute to having SMP/E point to copies of the datasets, and not trying your luck with the running stuff. On Sun, 12 Nov 2006 13:56:16 -0500, Shmuel Metz (Seymour J.) <[EMAIL PROTECTED]> wrote: >In <[EMAIL PROTECTED]>, on 11/09/2006 > at 10:08 PM, Bob Henry <[EMAIL PROTECTED]> said: > >>Is there a SAFE way to expand the size of SYS1.LINKLIB? > >Yes - on a target volume that you're not currently running from. Any >maintenance to the system you're running from puts you at risk. > >>I need to apply a PTF to a module in LINKLIB but I'm afraid it will >>cause it to go into a secondary extent. > >If you're talking about your live SYS1.LINKLIB then there may be other >risks as well. But it's not my dog. > >>Is there an easier (and safe) way to expand SYS1.LINKLIB? > >Safe? No, but safer. Make a copy with a larger primary. Rename >original. Rename copy. IPL. > >At you leisure, redo your maintenance strategy so that it does not >require updating the running system and you;ll save yourself a lot of >grief. > ---------------------------------------------------------------------- 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
