This is doable and no outages should be needed. However, be careful and slow and test, test, test.
You need to create the new library (I like putting .NEW at the end) Then once your copy is completed, do the following 1) Rename current to .old .new to current 2) Submit a job to open and close a different PROCxx DD statement. 3) Submit a job to open the PROC00 statement. 4) JES2 should reread the PROC00 and rebuild the TTR information DONE You may see a JES PROCLIB I/O Error message if a proc is requested before you complete the function. RESUBMIT after you are done. If you only have the one PROC00 statement in JES2, then do the following Create a new proclib with the sizing you want Do a $TPROCLIB to add it to JES2 EMPTY the old PROCLIB once the new PROCLIB is in place. Then plan a CYCLE of JES2 and take the new PROCLIB and replace the existing one with it. Though I would continue to use the $TPROCLIB in the JES2 Init Deck. I have not tested these procedures, I would work with this in a sandbox if possible. Lastly, I like jobs to have their own PROCLIB JCL statements (JCLLIB) to prevent these types of events. Only SYS1, IBM are in the JES2 JCL. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Dazzo, Matt > Sent: Monday, December 09, 2013 9:02 AM > To: [email protected] > Subject: JES2 Proclibs > > 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 > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
