On Mon, Dec 9, 2013 at 10:01 AM, 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? >
There are two ways to approach this: (1) the old way; and (2) the new way. I think, but am not sure, that if you use JCL to define the PROCLIB, then you must use option #1. In this option, you would RENAME the to-be-replaced PROCLIB DSN to "*.old". Now allocate a new, bigger, PDS using the old name ON THE SAME VOLUME! This latter is critical. Copy the *.old to the newly created version. Then get JES2 to close/reopen the PROCnn DD as Lizette indicated. The new way is possible if the PROCLIB concatenation had been done using the new dynamic PROCLIB feature. Use the $TPROCLIB as said by Lizette. ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HAS2A2A7/5.241 Another possibility, may be to uncatalog the old version of the proclib in question. Create and catalog a new version on a different volume. Copy the members from the old version to the new copy. Do a $DEL PROCLIB followed by a $ADD PROCLIB to redefine the entire PROCLIB concatenation. Of course, if any jobs go through conversion between the $DEL and $ADD, they will likely fail with a JCL error. > > Thanks Matt > > -- This is clearly another case of too many mad scientists, and not enough hunchbacks. Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
