ISPF FREED SYS1.PARMLIB
- From: Steve.Horein@xxxxxxxxxxxx (Steve Horein)
- Date: 30 Aug 2007 15:57:59 -0700
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!
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.
- Follow-Ups:
- Re: ISPF FREED SYS1.PARMLIB
- From: Lizette Koehler
- Re: ISPF FREED SYS1.PARMLIB
- Prev by Date: Re: Virtual Storage implementation
- Next by Date: Re: ISPF FREED SYS1.PARMLIB
- Previous by thread: Change Management Packages
- Next by thread: Re: ISPF FREED SYS1.PARMLIB
- Index(es):
Relevant Pages
|
|