Re: compress a proclib

2006-08-03 Thread Peter Ten Eyck
Thanks for your comments. I compressed the proclib in place at a very low activity time on the system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET

Re: compress a proclib

2006-08-03 Thread Ron and Jenny Hawkins
Bruce, That's how I remember it also. Ron -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Bruce Hewson Sent: Thursday, 3 August 2006 1:18 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: compress a proclib Actually, because JES2 normally

Re: compress a proclib

2006-08-02 Thread Mark Zelden
On Wed, 2 Aug 2006 15:25:15 -0500, Peter Ten Eyck [EMAIL PROTECTED] wrote: I have read various posting about the problems of compressing a PDS proclib. Then I'm wondering why you didn't find what you needed in the archives. I have a proclib call TEST.PROCLIB which out of space. snip

Re: compress a proclib

2006-08-02 Thread McKown, John
OK, maybe I'm living a charmed life. But if I need to compress a PROCLIB, I just run IEBCOPY with a DISP=SHR on it. I've never had a problem. The only problem that I can think of that might occur is if a job went to the converter and tried to use the PROCLIB during the actual compress process.

Re: compress a proclib

2006-08-02 Thread Mark Zelden
On Wed, 2 Aug 2006 15:49:24 -0500, McKown, John [EMAIL PROTECTED] wrote: OK, maybe I'm living a charmed life. But if I need to compress a PROCLIB, I just run IEBCOPY with a DISP=SHR on it. I've never had a problem. On Wed, 2 Aug 2006 15:46:36 -0500, Eric N. Bielefeld [EMAIL PROTECTED] wrote: I

Re: compress a proclib

2006-08-02 Thread Mark Zelden
On Wed, 2 Aug 2006 15:55:19 -0500, Mark Zelden [EMAIL PROTECTED] wrote: On Wed, 2 Aug 2006 15:49:24 -0500, McKown, John [EMAIL PROTECTED] wrote: OK, maybe I'm living a charmed life. But if I need to compress a PROCLIB, I just run IEBCOPY with a DISP=SHR on it. I've never had a problem. On Wed,

Re: compress a proclib

2006-08-02 Thread Lizette Koehler
I think there are actually a couple of solutions here. 1) Do not put user proclibs in JES2. Use the JCLLIB statement instead. 2) If you do put a user proclib in JES2 then make it with only primary allocation and no seconday. Allow for growth. If it fills up then use the JCLLIB statement 3)

Re: compress a proclib

2006-08-02 Thread Bruce Hewson
Actually, because JES2 normally does not have a ENQueue on its PROCLIBS, you should be able to compress it with DISP=OLD. That will stop any I/O errors for JCLLIBs. Regards Bruce Hewson -- For IBM-MAIN subscribe / signoff /