On Thu, 30 Aug 2007 17:57:48 -0500, Steve Horein wrote: >Hi all, >Ugh - Long days & short nights has taken it's toll on me. Instead of viewing >our shared SYS1.PARMLIB with 'V' in ISPF, I instead freed it with 'F'. Yeah I >know, F & V are not even on the same row on the keyboard. Now >SYS1.PARMLIB is 100% used. I've allocated 'SYS1.PARMLIB.SIZE' with the >original primary, 0 secondary. Would it be safe to: > >1) IEBCOPY the freed SYS1.PARMLIB into the SYS1.PARMLIB.SIZE, >2) rename the freed SYS1.PARMLIB to SYS1.PARMLIB.DONT.DELETE, >3) finally rename SYS1.PARMLIB.SIZE to SYS1.PARMLIB? > >Searching the archives makes me think I'd be fine, what with all of the topics >relating to compressing PARMLIB, but I'd rather ask outright about the whole >rename/swap idea. > >I have system specific PARMLIBs concatenated before SYS1.PARMLIB, so any >required changes could be made there if D37 issues arise before the next IPL. > >Thanks, and any suggestions would be helpful! Before you lose sleep over this, you might want to investigate the SETLOAD command to establish a (new) PARMLIB concatenation (with slightly different dataset names, then switch back when you have things pieced back together). Before you do that, however, you might want to be sure of your RACF (et al) situation - security folks tend to get huffy when PARMLIB shifts around on them. (Mostly they get that way when they know that auditors will be getting extra-huffy with the security folks for letting the sysprogs get too slippery.) -- Tom Schmidt Madison, WI
---------------------------------------------------------------------- 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
