RES: compress a proclib

2006-08-03 Thread Ituriel do Nascimento Neto
I've always compressed a PROCLIB with IEBCOPY (DISP=SHR) and never had a problem. But there is another possible solution : 1) Remove PROC00 from JES2 PROC and substitue it by PROCLIB statment in JES2PARM like sample below PROCLIB(PROC00) DD(001)=(DSNAME=SYS1.PROCLIB ),UNCONDITIONAL

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: RES: compress a proclib

2006-08-03 Thread Mark Zelden
on a regular basis. One other note... if you compress a PROCLIB allocated to *MASTER* (MSTJCLxx) and a proc is started with SUB=MSTR, you're SOL until you IPL if you run into strange results. There is no refresh trick. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead

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
) If you do need to compress a proclib in JES2 be aware during the compress process you can get I/O errors while the JCL is trying to convert. Just resubmit the job. To compress: Use DISP=SHR in the COMPRESS JCL (usually IEBCOPY). Next have a second batch job ready to go to access a proc

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 /