Thanks all for your input, I will test the options and make a decision. Is PDS86 file#182 on the CBT?
tks Matt -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Mark Zelden Sent: Monday, December 09, 2013 12:33 PM To: [email protected] Subject: Re: JES2 Proclibs On Mon, 9 Dec 2013 11:01:33 -0500, Dazzo, Matt <[email protected]> wrote: >We are running zos1.13, jes2. I have a production proclib in the jes2 proclib >search string. This proclib is a pds that is running out of directory blocks. >There are no enque's on the proclib except for when someone is working in it. >Finally the question, can I just create a new larger proclib, copy of the >members over and then rename the pds's or will JES2 become very unhappy? IPL >required? > >Thanks Matt This has been covered in the archives, including caveats many times. I know I have posted more than a couple of times. If you have dynamic PROCLIBs, you can remove / add a new one (copy old to new etc., volser doesn't matter, delete old from JES2, add new). If you have JES2 proclibs, do yourself a favor and download and use PDS86 (or commercial product if you have one) to SIMPLY increase the directory blocks. This will move some members to expand the directory and the PDS doesn't even need to be closed / reopened by JES2. You can do this with the dynamic proclibs also as a simple solution. If you want to force the reopen (if it makes you feel better), use $TPROCLIB(*). Allocating a new one / renaming if the PROCLIB if in JES2... not even sure that works without a bounce. The /*JOBPARM "trick" will reopen the PROCxx DD, but the extents are already known. I have always bounced JES2 when doing this. I've only used the "trick" after a compress of a PROCLIB PDS. Also note the "trick" does nothing if this is a MSTRJCLxx PROCLIB, nor does bouncing JES2. So if the proc is started via SUB=MSTR, forget the rename / trick. Also, a previous post mentions "no ENQ". That may or may not be true. In my shop I changed the PPT to the ENQ as soon as it was supported to keep newbies (and even some experienced sysprogs) and bad HSM rules or DASD mgmt jobs from ever trying to delete or move a PROCLIB. Finally, you may want to consider PDSE for the future to remove all the directory / compress considerations PDS PROCLIBs have. Cheers, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS ITIL v3 Foundation Certified mailto:[email protected] Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html Systems Programming expert at http://search390.techtarget.com/ateExperts/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
